🚀 go-pugleaf

LightSpeed C produces buggy desk accessories, and the example desk
accesory is dangerous!  Lightspeed C is one of those Cs that inserts  glue
routines to access global variables of desk accessories.  The global
variables are actually kept in a movable block of storage referenced in a
handle that lives in the DCE block of the desk accessory.  Bugs:
1) The compiler inserts code to dereference a handle and put a pointer to
the storage in regester A4, then reference global variables off of A4.
This preamble LOCKS the handle, and never unlocks, so your globals live
in a fixed block that contributes to heap fragmentation.
2) Since the preamble code locks the storage before your code ever gets
called, you can't even save the lock state of the handle and restore it
yourself - the state is already changed before your code ever gets called.
3) Since the storage is handled for you incorrectly, you can't manage it
yourself - the only slot for a handle to local storage in a desk accessory
is already taken up by the access made from this incorrect code.

4) The sample desk accessory given with the compiler is so wrong that it
scribbles on the memory of the application program and can cause random
crashes.  Do NOT Use it.  The problem is that the sample overrides a
system trap.  When the trap gets called, routines in the desk accessory
try to access the global variables of the desk accessory.  But since the
call is NOT a desk accessory call, it is a tool trap call, register A4
gets a garbage value.  (If you run it under MacBug in MacDraw, you can see
that register A4 has a 0 in it, when it should have the address of the
global block.)

5) The whole library gets included with every program, so a desk accessory
that should be about 900 bytes long takes up 4k.

It still is a real nicve system, I have written the manufacturer with the
above information, I'll let you know what the reply is.
Since the compiler generates machine code directly, there is no easy way
to look at this code.  
--- David Phillip Oster		-- "The goal of Computer Science is to
Arpa: oster@lapis.berkeley.edu  -- build something that will last at
Uucp: ucbvax!ucblapis!oster     -- least until we've finished building it."