Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!ihnp4!ihuxy!nowlin
From: nowlin@ihuxy.ATT.COM (Jerry Nowlin)
Newsgroups: comp.sys.atari.st
Subject: Re: Aztec C for the ST
Message-ID: <2543@ihuxy.ATT.COM>
Date: 2 Jun 88 13:12:32 GMT
Article-I.D.: ihuxy.2543
References: <2542@ihuxy.ATT.COM> <1395@megamax.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 43

In article <1395@megamax.UUCP>, michel@megamax.UUCP (Michel Rynderman) writes:
> In article <2542@ihuxy.ATT.COM> nowlin@ihuxy.ATT.COM (Jerry Nowlin) writes:
> >>I recently purchased Aztec C for the Atari ST from MANX Software Systems
> >>
> >>Problem 1.
> >>
> >>world program.  Unfortunately when I tried "cc hello" all I got was a
> >>temporary file and no ".o" file.  
> 
> cc probably stands for a compile and link utility. You needed to say
> "cc -c hello.c" to get a hello.o out of the compiler(just like UNIXtm) . 
> I have seen their product on the Mac and that is how it acts.
> "cc hello.c" will compiler and link, removing the object file.

I've been doing this long enough to have tried "-c".  No soap.  Even if
"-c" worked, the Aztec tutorial should have had it documented correctly.
I get real tired of documents with examples that have obviously never been
tried by anyone.  It reminds me of the joke:

Q: How many tech writers does it take to screw in a light bulb?
A: Just one, if there's a programmer around to explain it.

PLEASE don't include examples in manuals without someone trying them!

> >>Problem 2.
> >>I included a statement in my hello world that printed one line to standard
> >>error (stderr) in order to see how your buffering would effect the order of
> 
> I don't think there is a STDERR on the ST, so I wouldn't expect it to work.
> It should probably just go to STDOUT.

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.

By the way, I had to kludge stdio.h to work around a problem with stderr on
either my first version of Megamax C or Lattice C or both.  That's why I
tried an example using stderr on Aztec C in the first place.

Jerry Nowlin
(...!ihnp4!ihuxy!nowlin)