Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!husc6!endor!singer
From: singer@endor.UUCP
Newsgroups: comp.sys.mac.programmer
Subject: Re: A quick question: Lightspeed C, how does it work?
Keywords: Lightspeed C
Message-ID: <4710@husc6.harvard.edu>
Date: 4 Jun 88 20:42:50 GMT
References: <1407@its63b.ed.ac.uk>
Sender: news@husc6.harvard.edu
Reply-To: singer@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 27

In article <1407@its63b.ed.ac.uk> nick@lfcs.ed.ac.uk writes:
>Can I ask a very quick question?
>I intend to purchase Lightspeed C soon, but none of the reviews explain in
>detail how the "project" system works.
>   It is my understanding that a project file holds the *object code* and
>other book-keeping data, but *not* the source code. This means that (1)
>I can share source libraries between projects, and (2) any improvements I
>make to library stuff propagate (eventually) to any projects using it.
>This is what I want. I'd be disappointed if the project files actually
>included the source text as well...
>   Am I right?

	Completely correct.

		--Rich

Rich Siegel
THINK Technologies



Rich Siegel
Quality Assurance Technician
THINK Technologies Division, Symantec Corp.
Internet: singer@endor.harvard.edu
UUCP: ..harvard!endor!singer
Phone: (617) 275-4800 x305