🚀 go-pugleaf

ack@eleazar.dartmouth.edu (Andy J. Williams) writes:
>some things slip by.  So, you most likely had run it, corrupted your current
>memory into something which is barely holding together, ran it again and
>then your current instructions were misread by this corrupted memory and did
>something other than what you wanted.

I was under the impression that it was [ok, well, not impossible, but difficult]
to corrupt your project or Lightspeed C while your program is running, because
neither one of them is resident in memory at the time- your program gets
compiled,
and the _Launch trap is used to run it.  Because it gets sublaunched, it returns
to Lightspeed C when it's done.  Unless you specifically write the CODE
resources
back out, it should be really hard to corrupt your code for a second run.
(Blowing
the system away is an entirely different matter.)

"Look Ma! I wrote a program that drops into MacsBug!  And it does it so well!"

Tim Dierks
Tim_Dierks@cup.portal.com - dierks@ndmath.uucp - c4tkg3@irishmvs.bitnet