Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!sdcsvax!sdcc6!sdcc18!ss60f From: ss60f@sdcc18.ucsd.EDU (ss60f) Newsgroups: comp.sys.ibm.pc Subject: Re: C compilers? Message-ID: <579@sdcc18.ucsd.EDU> Date: Wed, 17-Dec-86 01:22:42 EST Article-I.D.: sdcc18.579 Posted: Wed Dec 17 01:22:42 1986 Date-Received: Wed, 17-Dec-86 23:49:06 EST References: <75800002@uiucdcsp> <998@hope.UUCP> Reply-To: ss60f@sdcc18.ucsd.edu.UUCP (ss60f) Organization: U.C. San Diego, Dept. of Anthropology Lines: 27 Summary: Aztec is good, but ... --------------- Re Aztec C: not a bad recommendation. I have the latest version (3.40) and have run a lot of code through it, with no problems. The executables it produces are smaller than many other compilers, and it does a reasonably good job at speed optimization. It is also nice to have the library source. I have had some trouble with the Aztec debuggers: they do not seem to work properly when the console is set to character mode, no echo. This is true of the new symbolic debugger as well as the older db. Although I haven't used it, my impression from ads/reviews is that the Codeview debugger that comes with the new Microsoft C compiler (4.00) is superior. The availability of good debugging tools can make a big difference in how much code you can turn out and how fast, so this is an important consideration. Microsoft also has good benchmark results. No library source, though. Dr. Dobb's Journal, Aug. 1986 has a good review of C compilers including Microsoft 4.00 and the next-to-latest version of Aztec C. -Jon Dart Dept. of Anthropology UCSD C-001 La Jolla, CA 92093 ss60f%sdcc18@sdcsvax.UCSD.EDU