🚀 go-pugleaf

In article <1995@husc6.UUCP>, stew@endor.harvard.edu (Stew Rubenstein) writes:
> In article <6186@dartvax.UUCP> earleh@dartvax.UUCP (Earle R. Horton) writes:
> >In article <1953@husc6.UUCP>, stew@endor.harvard.edu (Stew Rubenstein) writes:
> >> 
> >> All programs compiled with LightSpeed C WILL BREAK, GUARANTEED 100%,
> >> when Apple comes out with a 32 bit operating system for the Mac II or
> >Is this a general compiler problem, or is it, rather, specific to some
> >of the runtime libraries?
> 
> When I said "all" I meant "all."  Even if you don't even include MacTraps.
> The problem is in that little bit of code in segment 1 that gets prepended
> to all (that means every one without exception) applications.
The claim that all LSC applications execute code that assumes a 24 bit
addressing model is simply not true.  I am the primary developer at Apple of
the "A/UX Toolbox", the software that allows A/UX (Apple's UNIX) programs to
use the mac toolbox.  The A/UX Toolbox supports running programs that are
compiled as UNIX executables or Macintosh binaries.  In either case, the
application must be "well behaved".  This means, among other things, that
the application will be running in a 32 bit environment and cannot play nasty
games with the high bits of pointers.  Several months ago, I asked a friend
who uses LSC (or was that LSD?  No, that was another friend) to write a simple
program for me to test.  This program ran fine.  It is a very simple program
that only makes a few QuickDraw calls.  Sorry, I don't know what version of
LSC was used.  It is entirely possible that there are 32 bit violations in
code generated from LSC.  I only know that you don't necessarily get them in
every application.
						-- Rick Daley
						rpd@apple.UUCP
						ucbvax!sun!apple!rpd