Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!its From: csnjr@its63b.ed.ac.uk (Nick Rothwell) Newsgroups: comp.sys.mac.programmer Subject: A quick question: Lightspeed C, how does it work? Message-ID: <1407@its63b.ed.ac.uk> Date: 2 Jun 88 11:43:13 GMT Article-I.D.: its63b.1407 Reply-To: nick@lfcs.ed.ac.uk Organization: LFCS, University of Edinburgh Lines: 19 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? Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick%lfcs.ed.ac.uk@nss.cs.ucl.ac.uk !mcvax!ukc!lfcs!nick ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ ...while the builders of the cages sleep with bullets, bars and stone, they do not see your road to freedom that you build with flesh and bone.