🚀 go-pugleaf

In article <338@ihlpg.UUCP>, timborn@ihlpg.UUCP writes:
> 
> Now for my next query.  This is targeted primarily at Apple Corp. & UCSD.
> How can I get the OS to invoke my function "X" when it has trapped a fatal
> error?  

You can't.  You can get the operating system to try to continue
running your program (if you think it might help) by pressing <esc> at
the "type space to continue" prompt.

> How can I get more details on the memory layout, stack frame and
> global areas in Apple Pascal?

There is an Internal Architecture Guide available for version IV of the
system, so there *may* be a version for II.1 (on which the Apple
system is based).  If it isn't available from Apple, it may be available
from Softech Microsystems (619)451-1230.  Make sure you don't get the
guide for version IV because it is very different.

I know this doesn't help much, but you could always change to UCSD p-System
version IV.13 (available from Softech for a very costly price).
It *does* come with a symbolic debugger and it seems pretty nice, although
I don't use it.  It also has a number of nice features that the 
Apple Pascal system doesn't have.  It is also very slow on an Apple.
-- 
 From the virtual mind of Allyn Fratkin            allyn@UCSD.ARPA           or
                          UCSD EMU/Pascal Project  {ucbvax, decvax, ihnp4}
                          U.C. San Diego                         !sdcsvax!allyn

 "Generally you don't see that kind of behavior in a major appliance."