Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!ANDREW.CMU.EDU!rs4u#
From: rs4u#@ANDREW.CMU.EDU (Richard Siegel)
Newsgroups: comp.sys.mac
Subject: Lightspeed Pascal Problem...
Message-ID: <oUWYeLy00WI8ziw06L@andrew.cmu.edu>
Date: Mon, 20-Apr-87 11:19:35 EST
Article-I.D.: andrew.oUWYeLy00WI8ziw06L
Posted: Mon Apr 20 11:19:35 1987
Date-Received: Tue, 21-Apr-87 00:48:46 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 37


This isn't a bug per se, but it is a suggestion.

I was recently writing some code that involved calls to SetResLoad().
At one point, I had a double whammy: a bug in my program while
the ResLoad global was FALSE. What happened (of course) is that the program
dies, and since ResLoad is FALSE, Lightspeed Pascal crashes when it
tries to report the error. (In this case, I got a System Error 02, presumably
becuase LSP couldn't load a dialog to report the error). I get the thumbs-
down icon in my code, but no "bug box", just a crash.

My suggestion is the following:

	When LSP does a context switch from program to LSP environment, 
save the program's value of ResLoad, then call SetResLoad(TRUE), so 
that LSP doesn't die trying to do its thing. Likewise, restore 
the program's ResLoad then switching from LSP back to the program.

	This shouldn't be too terribly hard to implement, since LSP
saves lots of other stuff in context switches... And, it should prevent
system crashes when ResLoad inadvertently gets trashed, or if the
program dies while ResLoad is FALSE (which is what happened to me).

		--Rich


Richard M. Siegel
Materials Characterization Instrumentation Section
Mail Stop 231
NASA/Langley Research Center
Hampton, Virginia 23665
(804) 865-3036

Arpanet: rs4u@andrew.cmu.edu
Uucp: {your fave gateway}!seismo!andrew.cmu.edu!rs4u

Disclaimer? I don't even KNOW 'er!