Answering msg from Paul Edwards to rowan_crowe,
on Monday January 22 1996 at 23:13

 PE>> That code that that guy on the internet posted was pretty
 PE>> tricky, eh?  I might do something about using that when I
 PE>> figure out how I'm going to incorporate assembler into C.
 PE>> I'll have to write my own version though, since he didn't
 PE>> put a PD notice on his.  BFN.  Paul.

 PE> Actually, I don't suppose it's possible to get him to confirm
 PE> PDness of his code?

You could always email him and ask.

 r>> Quick terminology:

 r>> dword   4 bytes  (you call this a "fullword"?)
 r>> word    2 bytes  (and this a "halfword"?)

 PE> It's not unreasonable terminology.  A "word" is a machine's
 PE> native size.  The 386 is a 32-bit processor, hence a word
 PE> *should* be 32 bits.

Fair enough. I've been "brought up" in the 8 and 16 bit world, so
for me a word has always been 16 bytes.

In MoonRock I use "BYTE", "WORD" and
"DOUBLEWORD" or "DWORD". Perhaps I should use more
consistent terms such as char (or byte), integer and long. (Note I'm not
doing it for portability reasons, more to lessen confusion with people such
as yourself who might consider a "word" 32 bits).

---