Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!atha!lsuc!jimomura From: jimomura@lsuc.on.ca (Jim Omura) Newsgroups: comp.sys.atari.st Subject: Re: C compilers (was Re: C) Keywords: C Compilers Message-ID: <1991May2.023153.7191@lsuc.on.ca> Date: 2 May 91 02:31:53 GMT References: <5553@wucc.waseda.ac.jp> <11949@jarthur.Claremont.EDU> <1991Apr30.193021.10443@newcastle.ac.uk> Organization: Consultant, Toronto Lines: 36 In article <1991Apr30.193021.10443@newcastle.ac.uk> D.C.Halliday@newcastle.ac.uk (Dave Halliday) writes: > >There is also the question of ANSI compatibility. So Here is my revamped >table. > >name memory src price ANSI Debuger Notes >---------------------------------------------------------------------------- >GNU C 2Meg+ yes nil Y poor for ST UNIX origins >Sozobon C 520K yes nil N none?? PD I have source files from the '...st.sources' newsgroup that are supposed to be a source debugger for Sozobon C. I haven't even unpacked it yet though so I can't say more than that. Also Sozobon is NOT Public Domain. It's currently "Free". There's no guarantee that any or all future versions will also be free. Personally, I'm hoping they make at least one more free distribution which will be the definitive cleaned-up official version. After that, I don't care if they go "commercial". But I think they sort of owe it to the people who have helped them "beta test" this compiler. >Lattice V5 R 1Meg+ no #110 Y Low Level Optomiser 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? >So each compiler has its strengths. -- Jim Omura, 2A King George's Drive, Toronto, (416) 652-3880 lsuc!jimomura Byte Information eXchange: jimomura