Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!rutgers!mcnc!uvaarpa!murdoch!davinci.acc.Virginia.EDU!tmb
From: tmb@davinci.acc.Virginia.EDU (Thomas M. Breeden)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Modula-2 and Assembly
Message-ID: <1990Oct3.130455.11626@murdoch.acc.Virginia.EDU>
Date: 3 Oct 90 13:04:55 GMT
References: <4676@crash.cts.com>
Sender: news@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 20
Ireallyam: tmb

In article <4676@crash.cts.com> lkoop@pnet01.cts.com (Lamonte Koop) writes:
>
>    I'm about to go out of my mind here. ...
>...  You can also use INLINE or CODE procedures, which are basically
>inline lists of machine code (hex op-codes, the whole works...what fun; NO
>mnemonics, labels, etc...just the pure machine code...),...
>       LaMonte

If you have future needs to do more INLINE or CODE use, I've got a
definition module, "Assembly.def", which contains a couple of hundred
CONSTs giving mnemonic names for 68K opcodes, bitfields, registers, etc.

This makes it somewhat easier to INLINE a chunk of machine code, even
without an assembler.

Anyone interested in a copy?

Tom Breeden
tmb@virginia.edu  -->> Internet
tmb@virginia      -->> BITNET