🚀 go-pugleaf

In article <194@cbmcel.UUCP>, Martin S. Stoller writes:

> In article <184a3cc5.ARN04295@adspdk.UUCP> hclausen@adspdk.UUCP writes:
> >In article <CEDMAN.90Nov28142350@lynx.ps.uci.edu>, Carl Edman writes:
> >
> >   An Asm programmer has to know about bits, registers, offsets etc. that a
> >C programmer wouldn't bother about. 
>
> If a C programmer knows nothing about bits, registers, offsets, vectors,
> etc... THEN SHE/HE IS NOT A C PROGRAMMER!!!  There are many simple
> and easy ways in C to play with bits, like >> and << and ~ and & and |
> and stuff like that.

   Now, that's quite a different matter. I do know all about binary
aritmetics, bitfields etc., and how to use this for speed.

   What I don't know, and don't want to know, are the exact locations and
functions of Agnus, Denise & Paula registers, CPU status registers etc.,
nor do I take much interest in the particular CPU I'm running on, as long
as it doesn't force me to do nasty things, like the older Intel CPU's did.

> How do you think I can programm a library, with proper
> function calls, which will make sence to the system???  And I very well
> know what a REGISTER is; after all, it IS a C keyword :^).

   I stated above that the Asm programmer needs to know LOTS more details
than the C programmer does, and that's the fact.


                                             -Henrik
______________________________________________________________________________
| Henrik Clausen, Graffiti Data | If the Doors of Perception where cleansed, |
| ...{pyramid|rutgers}!cbmvax!  | Man would see Reality as it is - Infinite. |
\______cbmehq!adspdk!hclausen___|_________________________________W. Blake___/