Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.sys.apple Subject: Re: c compiler Message-ID: <7446@brl-smoke.ARPA> Date: 12 Mar 88 22:27:43 GMT References: <1506@netmbx.UUCP> <7628@agate.BERKELEY.EDU> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) Distribution: comp.sys.apple Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 Keywords: system In article <7628@agate.BERKELEY.EDU> laba-4an@web3h.berkeley.edu.UUCP (Andy McFadden) writes: >Does the Aztec compiler support the UNIX system calls, or just the generic >ones like fopen? Is curses supported [yes, I'm dreaming]? Obviously, no Apple II C compiler is likely to support fork(), ptrace(), etc. Manx's Aztec C65 does have open(), read(), etc. and a limited subset of ioctl(). Curses is not supported, but there is an alternate screen display library included, as well as a library simple plotting graphics routines. I've used Aztec C on my Apple II for several years and am generally pleased with it. Its two biggest drawbacks are that it works only in 8-bit mode and it has limited support; apparently other computers such as the Macintosh are more profitable markets. An annoying but perhaps inevitable feature is that it takes a long time to compile even moderately large sources, and it is best used with a hard disk (two 5.25" disks is the absolute minimum but is too tedious to recommend).