suitti@haddock.ima.isc.com (Stephen Uitti) (05/23/89)
In article <1886@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes: >In article <7385@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >>Incidentally, we're using the word "instant" in, shall we say, a >>creative manner, eh? > Not really. LSC's compilation speed on a regular Mac II is typically 20K lines/minute. I'm used to more like 7K on "big UNIX" machines. On my Mac II, link time can be measured, but i wouldn't use the phrase "wait for the link". Similar things can be said for running. >>complaints about the LSC interface, good as it is overall, is that >>there are too many buried features. Stuff is supposed to be advertised >>in the menus and dialogues. > The ability to pop up a list of #include files is documented. I >quote: You may be wasting your breath. A UNIX box can scarcely be used without the manuals within reach. Mac users get so complacent. When i get a new piece of software for the Mac, i *always* just run it first. I don't think i even finished reading the LSC manuals cover to cover a second time (but then i only read most manuals once, anyway). I like the includes pop up. They need to be attached to the editor window, so that you have some idea what the includes refer to. It could have been designed as a single menu entry, with a side menu of the include files for the active editor window. These pull to the side menus are becoming more popular as applications get more complex. The user interface issue that bugs me the most is this. I get some C source from somewhere else (MSDOS, UNIX, etc.), and i want to port it to LSC. I create a folder and copy a template project to it (hello world). I throw the sources into the folder. I fire up the LSC from the project, "remove" the hello.c source, and add the new sources. I then go through compiles until the includes work and "add" the appropriate libraries. To "add" the libraries, i get a standard "open file" dialogue box and rummage through the LSC folder. Invariably, when the project builds, the "open" dialogue is still set to the LSC folder. It never gets saved in the project folder. LSC isn't the only application that does things this way. It is pervasive on the Mac that there is only one "connected directory" (to use some UNIX terminology). This doesn't make it "right". Of course i also want "#if defined(x) && !defined(y)" to work. (Don't tell me to convert ifdef mactros to numeric ones.) For that matter, i can hardly wait for a real ANSI C compiler. Of course, i can hardly wait for the standard to be ratified. Stephen.
mithomas@bsu-cs.bsu.edu (Michael Thomas Niehaus) (08/11/89)
For those of you who are wanting to upgrade your copy of Think's Lightspeed
C (or whatever they care to call it) you can call this number with your
credit card ready:
1-800-441-7234
The cost of the upgrade is $69 plus $5 for shipping and handling. In addition,
Symantec is having a special offer to those upgrading. For $19.95 (or
something like that) you can get the "Macintosh Programming Primer" as well.
The total for both pieces is $93.50. For an additional $2.50 you can have
it shipped UPS Blue (second day).
The representative that I talked to today said that there was a good backlog,
but that shouldn't delay shipment for too long.
-Michael
--
Michael Niehaus UUCP: <backbones>!{iuvax,pur-ee}!bsu-cs!mithomas
Apple Student Rep ARPA: mithomas@bsu-cs.bsu.edu
Ball State University AppleLink: ST0374 (from UUCP: st0374@applelink.apple.com)