home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!sersun1!okes
- From: okes@essex.ac.uk (Simon Oke)
- Newsgroups: comp.sys.atari.st
- Subject: Re: Porky pig.
- Message-ID: <OKES.93Jan11165337@SunLab42.essex.ac.uk>
- Date: 11 Jan 93 16:53:37 GMT
- References: <5JAN93.09425752@cc4.crl.aecl.ca><C0Furt.I67@news.cso.uiuc.edu>,
- <H.ea.0kgtRS0BsQs@semprini.tdkcs.waterloo.on.ca>
- <1993Jan11.021216.13462@bsu-ucs>
- Sender: news@sersun1.essex.ac.uk
- Organization: Department of Computer Science, University of Essex, UK.
- Lines: 31
- In-reply-to: 01mbmccabe@leo.bsuvc.bsu.edu's message of 11 Jan 93 07:12:16 GMT
-
- In article <1993Jan11.021216.13462@bsu-ucs> 01mbmccabe@leo.bsuvc.bsu.edu writes:
- |My thoughts to that point (thinking more generally) are that MOST people don't
- |NEED to program in GNU C++. This places a hard-drive back into the nice-but-
- |still-a-luxury catagory. Sorry, it's still $$ (and a maybe a smattering of
- |nostalgia) that holds me out of the clone-realm. I'll probably cross the
- |threshhold some time after a hard-drive for this ST costs more than a complete
- |clone system. And that's not likely to happen soon.
- |
- I don't need G++ either. However, I couldn't do any of my project work at
- home without GCC. For example, the code I wrote last year compiled perfectly
- happily using GCC on a SPARCstation. When I took it home to work on, I tried
- all 3 compilers which I had available.
-
- 1. Lattice C.
- Got around the problem of it not having a proper make by merging all the
- files into one. Finally compiled after a few options had been changed.
- Code ran and exited immediately, saying that the stack was full.
-
- 2. Sozobon C.
- Didn't even compile. Got half-way through and said that there was a fatal
- bug IN THE COMPILER.
-
- 3. GCC.
- Worked first time.
-
- Boy is GCC useful. It eats up a few acres of disk space, but I'm glad I've
- got it.
-
- --
- Simon Oke, 3rd year Computer Science
- undergraduate at the University of Essex, UK.
-