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:35
subject: #8918-#68000 ASM Language

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

[Continued]

I was real pleased with the language, but at that time I didn't know enough
about how to build an assembler to implement it.  Now I do.

Unfortunately, the technology keeps passing me by.  By the time I had the 8080
syntax defined, along came the Z80, with extra addressing modes and
instructions.  By the time I got those figured out, I was suddenly in the 68000
business.  Gotta learn to work faster!

When I first started programming for the 68000, I had a real problem with some
of the branch instructions.  Like DBcc, for example, NEVER seems to do what the
instruction seems to say.  So I wrote a structured preprocessor for the
assembler.  I had constructs like IF..THEN..ELSE..ENDIF, WHILE..ENDWHILE,  and
FOR.. ENDFOR. I wrote a prototype in Turbo Pascal for my PC, and it worked like
a champ.  I was truly surprised at how easy it is. Never implemented it for
SK*DOS (early on, the development tools weren't up to the task), but it's still
in my job jar.

I don't need help building the assembler.  What I _COULD_ use lots of help on
is defining the language.  More on this in the next message:

[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™.