Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!pasteur!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!hp4nl!ruuinf!edwin
From: edwin@ruuinf.UUCP (Edwin Kremer)
Newsgroups: comp.sys.atari.st
Subject: Re: Is there a good (and fast) C-compiler for the ST?
Summary: Try Turbo C from Heimsoeth and Borland
Message-ID: <1089@ruuinf.UUCP>
Date: 30 Jan 89 14:56:22 GMT
References: <774@draken.nada.kth.se> <775@draken.nada.kth.se>
Organization: Univ of Utrecht, Dept of CS
Lines: 29

In article <775@draken.nada.kth.se>, matsl@nada.kth.se (Mats Luthman) writes:
> I would like to have some brief information on C-compilers currently
> available for the ST. I am iterested in compilation speed (especially
> when run on a hard disk if that has an influence on it), prices,
> kind of user interface, if there is a lint function or support for
> prototypes and so on.

Turbo C is fast (sorry, no hard statistics); I've seen comparison
against Mark Williams, Lattice, Laser and Aztec. Turbo C beats them all,
although MWC has much better debug facilities.

Turbo C is rather cheap, in the Netherlands around Dfl. 250,-, which is
about $120

Two user interfaces: one for commandline Shell freak, the other window
GEM oriented (like Turbo C for MS-DOS).

Supports prototyping (it's use strongly recommended), is full ANSI standard.

Fast execution, uses registers for passing parameters to a function rather
than the stack. Functions that have a variable number of arguments are
an exeception to this, of course...

						--[ Edwin ]--
-- 
Edwin Kremer, Department of Computer Science, University of Utrecht
Padualaan 14,  P.O. Box 80.089,  3508 TB  Utrecht,  The Netherlands
Phone: +31 - 30 - 534104        |  UUCP    : ...!hp4nl!ruuinf!edwin
    "I speak for myself ..."    |  INTERNET: edwin@cs.ruu.nl