Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!usc!sdsu!crash!alen
From: alen@crash.cts.com (Alen Shapiro)
Newsgroups: comp.sys.mac.programmer
Subject: LSC 4.0; possible sublaunch side-effect problem?
Keywords: THINK C launch sublaunch parameters appparmhandle
Message-ID: <1229@crash.cts.com>
Date: 19 Jan 90 21:50:53 GMT
Reply-To: alen@crash.cts.com (Alen Shapiro)
Organization: Crash TimeSharing, El Cajon, CA
Lines: 22

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