🚀 go-pugleaf

In article <8902100715.AA16566@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>	Gee Jim, I don't know of any Make's that *can* use Execute(), god
>knows I've tried.  The problem, of course, is that one needs to retrieve the
>exit code ...
>
>	I would gladly use Execute() if I could retrieve the exit code.

After calling Execute(), IoErr() returns the DOS exit code.  If I remember
correctly, this was added in 1.2, and Andy Finkel discussed it some on BIX.
I don't remember seeing it documented anywhere else.

>	That is, assuming the compiler makers fix their exit() code properly.
>I don't know about Lattice, but Aztec does NOT set the DOS exit code fields
>(so, for example, even if I did use Execute() and it did return the exit code,
>it would still not work with Aztec's cc & other utilities, or any programs
>I write).
>
>					-Matt

Lattice 5.0 sets the exit code properly.  This seems to have been added
when they added all the support for standard 1.3 resident programs--when
compatibility with the standards started becoming more important, as
Jimm pointed out.

I have a version of the make on Fish disk 69 which I modified (trivially)
to use Execute() instead of the Manx fexec().  It retrieves the exit code 
using IoErr().  To test it, I just wrote a test program (test.c) which
does nothing but exit(20), and a makefile which invokes test.  Typing 
'make' returns a very gratifying "test failed (returncode 20)".  All the
parts of Lattice's compiler work just as nicely, and most can be made
resident in the standard way.

So, Jimm is asking for something completely reasonable.  It works with
Lattice 5.0.

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell U.