Newsgroups: comp.sys.atari.st
Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!maccs!johns
From: johns@maccs.dcss.mcmaster.ca (Conan the Barbarian)
Subject: Re: C compilers (was Re: C)
Message-ID: <2820235B.4097@maccs.dcss.mcmaster.ca>
Keywords: C Compilers
Organization: McMaster University, Hamilton, Ontario, Canada
References: <11949@jarthur.Claremont.EDU> <1991Apr30.193021.10443@newcastle.ac.uk> <1991May2.023153.7191@lsuc.on.ca>
Date: Thu, 2 May 91 14:34:03 GMT

In article <1991May2.023153.7191@lsuc.on.ca> jimomura@lsuc.on.ca (Jim Omura) writes:
>[...]
>     I'm thinking about buying a Lattice.  I'm working with
>a 1040ST, and when you have a bunch of ACC's loaded, I'm wondering
>if I'll might have a problem.  It is really that touchy about
>RAM?
>[...]

	My recommendation goes to Lattice 5.  A friend of mine stepped up
to Lattice from Laser, and I've played with Turbo some.  The things that
might make me go with Turbo are the excellent help facility and the debugger,
but the Lattice library manuals are pretty good so the help that Turbo
provides is only a nominal.  As for the debugger, who has bugs??  :-)

	Lattice was not practical from it's editor/environment.  It takes up
too much memory. (That's on a 1Meg machine, with HD) You can compile single
files nicely from the environment, but if you need make like I did, it
doesn't work out too nicely.  I tried to install make as a tool so I could
run it with a single keypress, but I ran out of memory.  But I prefer the CLI
anyway, and then no problems.
 
-- 
John Schmitt
johns@maccs.dcss.mcmaster.ca
...!unet!utai!utgpu!maccs!johns