>Well I like it! Although adding the extra 0 to an address can be a pain
>sometimes indeed... But an intelligent assembler should be able to see the
>difference between an address and a label, too bad they usually don't.
How could an assembler state whether BADH is a hex number or a label in a
single pass?
>>H's are indeed a standard Intel convention *BUT REMEMBER* Zilog enhanced
>>the 8080 architecture with their Z80, including the assembler!!! So don't
>>make a step backwards, please.
>
>Then why does Zilog use H-suffixes in all their official documentation?
>(Z80, Z380, etc.)
Because they use a bad 8080-friendly assembler 8;)
Trivia: Most of the Motorola 680x0 series official documentation listings
are written in UPPER CASE when it's officially discouraged!
Trivia 2: Most of the Amiga system software is *NOT COMPLIANT* to the
official Style Guide!!
The # prefix was introduced as a more convenient *alternate* way of
specifying a hex number. It's not officially endorsed as the only supported
method!
People involved in writing the official docs felt more confortable with the
H suffixes, just like the M680x0 official coders felt confortable writing
with the caps locked.
MARK #02 <- PUN INTENDED! 8;D
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****