Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 alpha 5/22/85; site cbosgd.UUCP Path: utzoo!watmath!clyde!cbosgd!db From: db@cbosgd.UUCP (J. Muir) Newsgroups: net.micro.mac Subject: Re: LighspeedC -- A Review (long!) Message-ID: <1987@cbosgd.UUCP> Date: Thu, 10-Apr-86 13:08:37 EST Article-I.D.: cbosgd.1987 Posted: Thu Apr 10 13:08:37 1986 Date-Received: Fri, 11-Apr-86 01:26:21 EST References: <848@harvard.UUCP> Reply-To: db@cbosgd.UUCP (J. Muir) Organization: The Bohemian Grove Lines: 34 Keywords: Aztec C,compilation environment In article <848@harvard.UUCP> matthews@harvard.UUCP (Jim Matthews) writes: > > There have been a couple of postings about the new LightspeedC >compiler, and since I recently ported a large (2200 line) program from >Aztec to that environment, I figured that the net might be interested in >my reaction. > : >To edit a source file you >just double-click on a name -- avoiding both the typing of Aztec and the >SFGetFile dialog of other systems. Minor point, but: Aztec 1.06g (which the author later mentions using for his comparisions) has the "compromise" menu-bar/command-line user interface in its shell. If the current directory has any .c files in it, you get Source and Compile menus added to the bar. You can then put a check next to the source file of interest and edit, compile, assemble, link, and/or execute by simply selecting the appropriate item on the Compile menu. There are also Compile options for automatic sequences. This is much nicer than having to type commands to the shell (especially without a history mechanism) but it's a little bizarre to watch. This scheme works best for relatively small applications consisting of a single source file. If you need link options you can set them once using the LFLAGS environment variable. Similarly, I set the environment so the edit item uses the name "vi" for the editor (Z so renamed to avoid typing frustrations; you can use that to get MDS Edit or whatever editor you use). I believe FLAGS variables also exist for the compiler and assembler. For larger applications, you'd want to use the Aztec make facility, which I haven't used myself because I haven't written any large applications, nor am I anxious to plunge into makefile-writing (I sure hope New Make catches on and Macintosh C packages pick up its makefile style). Dave Bursik/..cbosgd!db