Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!bsu-cs!mithomas
From: mithomas@bsu-cs.bsu.edu (Michael Thomas Niehaus)
Newsgroups: comp.sys.mac
Subject: Re: What is the Best "C" compiler program out there?
Message-ID: <7892@bsu-cs.bsu.edu>
Date: 22 Jun 89 21:04:34 GMT
References: <12292@netnews.upenn.edu> <4728@ucdavis.ucdavis.edu>
Distribution: usa
Organization: CS Dept, Ball St U, Muncie, IN, USA
Lines: 51

In article <4728@ucdavis.ucdavis.edu>, heberlei@iris.ucdavis.edu (Todd) writes:
> Price: The price for THINK C has gone up where I shop from $120 to
> $170, but that is still a very good price for a compiler (I orignally
> paid $225 for mine with a student discount).  However, you will
> probably be spending at least as much money in books (this is probably
> true for any compiler).

I recently purchased a copy of Lightspeed C, and I must say that I am
not disappointed.  (I bought my copy from the Mac Zone for $159.)  I use
it on a Mac SE with a 20MB hard drive and 1MB of memory without any problems
(well, almost -- see below).  The make facilities, project management features,
fast compilation, etc. make it an excellent buy.

> System: I believe there are a number of whistle and bells with Think C
> which requires 2 Megs or more.  However, I am sure the basic stuff
> works fine with one Meg (BUT CHECK to make sure).  The more souped up
> your machine the better.  Software development will push any machine
> to the edge, so you may want to consider putting some more money into
> your machine at a later date (like when you find some money :-)

Yes, the basic compiler works very well with 1MB.  However, in order to
get full use out of the integrated debugger, you need 2MB.  The debugger
is excellent, as well.

[A quick note:
  I wrote an FKEY that does an ExitToShell so that I could get rid of the
  Finder, freeing up 160K of memory.  By doing that and adjusting the
  memory sizes of the debugger, my application, and the compiler, I can
  run under MultiFinder with 1MB of memory and be able to use the debugger.
  The debugger does require MultiFinder.  But there is one problem with this:
  I cannot quit from Lightspeed C; the machine will crash (of course: no
  Finder).
]

As for documentation, you will need to spend a good amount on books.  I
have Inside Mac volumes 1 and 2, How to Write Macintosh Software, and
Macintosh Programming Secrets (Knaster's two books).  They give you a good
idea of what is going on, but don't expect them to hold your hand all the
way through.

Right now, I am trying to get a copy of the _Programmer's Introduction to
the Macintosh_ from the Apple Programmer's and Developer's Association.
It is supposed to do a good job of helping the struggling Mac programmer
(that's me, although I am getting better).

-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)