[comp.sys.mac.programmer] LSC 4.0; possible sublaunch side-effect problem?

alen@crash.cts.com (Alen Shapiro) (01/20/90)

I have a LSC4.0 program that sublaunches an application with a
document (finally got it working - thanks to all the netters
who helped). The program works just fine providing it is run
from a compiled application and not from the THINKC project
("run" command).

The symptoms are that my sublaunched program works fine, completes,
hands control back to the parent (which is awaiting a char to continue).
On quitting the parent, control is not sucessfully returned to the
THINK C project, which goes into an infinite recursion issuing
BEEPs and eventually running out of stack. 

Is this a known problem with the THINK C environment? Does that environment
not protect the parameter area (that it uses when the project is restarted
after a user program is run) across program execution. Since the parameter
area is a system-wide global, I may be doing something stupid with that.
I have a small bug demonstration program which I can post or mail if there
is any interest.

--alen the Lisa slayer (trying to slay macs now!!)
...alen%shappy.uucp@crash.cts.com (a mac+ uucp host - what a concept!!)
...alen@crash.cts.com