Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mit-eddie!husc6!endor!siegel From: siegel@endor.harvard.edu (Rich Siegel) Newsgroups: comp.sys.mac.programmer Subject: Re: Lightspeed Pascal 2.0 Keywords: lightspeed, pascal, review, pro, con Message-ID: <773@husc6.harvard.edu> Date: 6 Dec 88 15:38:20 GMT References: <2219@ilium.cs.swarthmore.edu> Sender: news@husc6.harvard.edu Reply-To: siegel@endor.UUCP (Rich Siegel) Organization: Symantec/THINK Technologies, Bedford, MA Lines: 40 In article <2219@ilium.cs.swarthmore.edu> jackiw@cs.swarthmore.edu (Nick Jackiw) writes: > >- MAJOR ANNOYANCE: Lightspeed stamps its own thumb-print on every application >you build. Go into ResEdit and LO! An extra resource not in your rez-file, >called--oddly enough--'LSP' (Id#2000; Size 18; locked+preload). If you zap it, >you zap your application too... What's the deal with this? It seems like a >completely gratuitous bit of egoism on LSP's part. The resource data is fixed Since you don't have a clue as to what the LSP resource does, why don't you ASK, instead of assuming? As it happens, the LSP resource is for runtimeerror recovery; when a Pascal runtime error occurs (range checking, overflow, file i/o error, etc), control is passed to the LSP resource. The standard LSP resource simply does a DebugStr which reports the error. It is possible for a programmer to write a different LSP resource which reports the error in a nicer fashion. >new 'LINK error' window doesn't help you find what segment or source file the >bad-link reference occurred in...). If LSP 3.0 offers as much of a change as >2.0, I'll keep on upgradin'. For a failed link, the Link Errors window simply lists the undefined symbols. However, if you then choose "Check Link", the Link Errors window will show you the files from which the undefined symbols are referenced. --Rich Rich Siegel Staff Software Developer THINK Technologies Division, Symantec Corp. Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel Phone: (617) 275-4800 x305 Any opinions stated in this article do not necessarily reflect the views or policies of Symantec Corporation or its employees.