Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK Pascal
Message-ID: <2524@husc6.harvard.edu>
Date: 29 Aug 89 02:32:15 GMT
References: <878@eutrc3.urc.tue.nl>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 47

In article <878@eutrc3.urc.tue.nl> rcbaem@eutrc3.uucp writes:
>
> Could it be:
>1) The resource manager can't handle the project anymore? Since LSP
>   stores all info in separate resources this could be a possibility.

	Your project document may have gotten munged. Are you using
MacroMaker? According to our Tech Support guys, MacroMaker has a known
track record of smashing projects.

>2) My LSP is infected with a virus? (never had one ever, but who knows?
>   nVIR was found on one of our University's HDs...)

	Possibly, but not likely. Worth checking into, though.

>3) LSP can't handle very large procedures? (The code is still <32K
>   though, and the source file hasn't reached the upper module
>   size limit either)

	Not likely.

>4) I have too many variables to fit on the program's stack. (doubt
>   it, I have had programs with many more variables)

	Same; the compiler will give you an error if there's not enough
stack space to invoke a procedure or if too many locals are declared.

>5) LSP runs out of memory while compiling or linking? Doubt it because
>   I have 2M of it..

	You should get a warning message before you get a crash. Trust me. :-)

R.



~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"There is no personal problem which cannot be solved by sufficient
application of high explosives."

~~~~~~~~~~~~~~~