TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Jack Crenshaw 72325,1327 (X)
from: Jack Crenshaw 72325,1327
date: 1990-12-27 23:53:42
subject: #8919-#68000 ASM Language

#: 8920 S12/OS9/68000 (OSK)
    27-Dec-90  23:53:42
Sb: #8919-#68000 ASM Language
Fm: Jack Crenshaw 72325,1327
To: Jack Crenshaw 72325,1327 (X)

[Continued]

The first decision is:  Do I keep the conventional format (label, mnemonic,
operands) ... in other words, try to remain as faithful to convention as
possible, or do I go for the A=B approach?

The next decision is:  How to handle all the addressing modes, sizes, etc.

Either way I go, I obviously have to allow for the generation of any
instruction that the normal assembler provides.

The size parameters give me fits, too.  I'm sorta toying with the idea of a
size declaration.  In other words, you could declare D0, say, to be size byte. 
From then on, until you redeclare it, every reference to D0  would produce a
byte instruction.  Saves all the '.B's.

[More]



There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.