Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!ames!husc6!spdcc!merk!alliant!rosenkra
From: rosenkra@Alliant.COM (Bill Rosenkranz)
Newsgroups: comp.sys.atari.st
Subject: Re: Aztec C for the ST
Message-ID: <1904@alliant.Alliant.COM>
Date: 3 Jun 88 17:32:28 GMT
Article-I.D.: alliant.1904
References: <2542@ihuxy.ATT.COM> <1395@megamax.UUCP> <2543@ihuxy.ATT.COM>
Reply-To: rosenkra@alliant.UUCP (Bill Rosenkranz)
Organization: Alliant Computer Systems, Littleton, MA
Lines: 26


---

In article <2543@ihuxy.ATT.COM> nowlin@ihuxy.ATT.COM (Jerry Nowlin) writes:
->In article <1395@megamax.UUCP>, michel@megamax.UUCP (Michel Rynderman) writes
->> In article <2542@ihuxy.ATT.COM> nowlin@ihuxy.ATT.COM (Jerry Nowlin) writes:
->> >>
->> >>Problem 1. [discuss problems and rebutt response...]
->
->The point is, if there is no stderr on the ST then they shouldn't have
->referred to it in their documentation at all other than to state that
->stderr wouldn't work.  If there was stderr and it was the same as stdout
->their documentation should have stated that.  Their document was a great
->example of misinformation when it came to stderr.
->

good points about bad docs. its a shame because i, too, have been waiting
to see just how good this compiler would be. sounds like it needs some work
yet. i guess i'll stick with good 'ol alcyon (maybe slow but it works...)
if the problem is just cc, there are several cc programs (w/src) available
(i wrote my own way back when) which could be converted. but it sounds like
the libraries are brain damaged and that's just too much of a hassle to fix,
even with say dlibs. i'm tired of hacking at system software just to get it
to work the way it should (i.e. reasonably close to un*x).

-bill