Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!ukma!nrl-cmf!ames!amdahl!kucharsk From: kucharsk@amdahl.uts.amdahl.com (William Kucharski) Newsgroups: comp.sys.mac.programmer Subject: Re: C's that do not impose the 32K global data limit Keywords: Which ones? How good are they? Message-ID: <97JyGc6vzM1010WSid.@amdahl.uts.amdahl.com> Date: 13 Jul 88 23:30:45 GMT References: <320@intek01.UUCP> <6319@dcatla.UUCP> <402@dbase.UUCP> Reply-To: kucharsk@amdahl.uts.amdahl.com (William Kucharski) Organization: Amdahl Coup, UTS Products Hen House Lines: 57 In article <402@dbase.UUCP> drc@dbase.UUCP (Dennis Cohen) writes: >In article <6319@dcatla.UUCP>, dxjsb@dcatla.UUCP (Jack S. Brindle) writes: >> Mark McWiggins writes: >> >> Well, My biggest problem with Manx/Aztec C is their inability to >> properly support the product. I've been a user since the product was >> originally released by in the summer of 1984. The current version is 3.4b, ^^^^ >The current version, the one I've had for about eight or nine months is 3.6A. ^^^^ Where did you get 3.6A? When I ordered my copy of Aztec C in May (something I now pretty much write off as a "live and learn" experience) they sent me 3.4b. So either Manx was nasty and sent me an older version, or somehow you got a copy of an update. My biggest Aztec gripes: 1) Color <> Mac II problems. Manx says it will be taken care of "not in our next update, but the one after that" 2) If Pyro! activates itself while you're in "Z" upon returning the program crashes and dumps itself into MacsBug 3) Control Panel items (cdevs) are not available unless you put the Shell in the System Folder and start from there - otherwise it won't find any when you pull down the Control Panel 4) The example programs aren't written real well - some leave large white areas behind a window when a window is moved, and "Explorer," a DA for searching through RAM, has a typo that gives an extra character in the title bar of its window 5) No aliasing in the shell. If you want "rm -i" to be your default rather than just "rm," you can't do it. 6) The screen uses a different typeface and size than the editor. Therefore, when you "cat" something it won't look the same as it does in the editor. (To get around this, I wrote a "more" routine which sets the typeface to the same type and size as used by the editor). Basically, their interface is something you have to kind of "get along with." All I can say is "try before you buy." -- William Kucharski ARPA: kucharsk@uts.amdahl.com UUCP: ...!{ames,decwrl,sun,uunet}!amdahl!kucharsk Disclaimer: The opinions expressed above are my own, and may not agree with those of any other sentient being, not to mention those of my employer.