Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uokvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!uokvax!emjej
From: emjej@uokvax.UUCP
Newsgroups: net.micro.6809
Subject: XLisp 1.2 compiled for OS-9
Message-ID: <3500074@uokvax.UUCP>
Date: Wed, 13-Feb-85 17:20:00 EST
Article-I.D.: uokvax.3500074
Posted: Wed Feb 13 17:20:00 1985
Date-Received: Sat, 16-Feb-85 05:38:23 EST
Lines: 17
Nf-ID: #N:uokvax:3500074:000:847
Nf-From: uokvax!emjej    Feb 13 16:20:00 1985


XLisp 1.2, recently posted to the net, compiles under OS-9/6809. With Microware
C, it turns into 29,047 bytes module size (5K more than XLisp 1.1, although I'd
put in system, shell, chd, and chx hacks into XLisp 1.1 by that time).

Be warned, though: I had to hack on all the declarations of pointers to
jmp_buf. The compiler had two choices of what to treat such declarations as,
and it made it differently from other C compilers. (Some of you out there
may actually think that K&R specifies what happens. That's a comforting belief,
I'm sure, but then, so are the Tooth Fairy and Santa Claus--perhaps you should
try to hang on to them, too.) xlisp.c, xleval.c, and xlread.c require some
changes. These made, it seems to work just fine.

BTW--I have talked to Microware about this C compiler problem (?!).
They're aware of it.

						James Jones