🚀 go-pugleaf

---

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