Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!uflorida!gatech!dcatla!dxjsb
From: dxjsb@dcatla.UUCP (Jack S. Brindle)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Aztec C Problems
Keywords: Manx, sdb, debugger
Message-ID: <7984@dcatla.UUCP>
Date: 15 Aug 88 15:35:14 GMT
References: <15112@shemp.CS.UCLA.EDU> <2669@pt.cs.cmu.edu> <8808131413.AA16229@gerrard.csri.toronto.edu>
Reply-To: dxjsb@sunb.UUCP (Jack S. Brindle)
Distribution: na
Organization: DCA Inc., Alpharetta, GA
Lines: 44

In article <8808131413.AA16229@gerrard.csri.toronto.edu> vg@csri.toronto.edu (Victor Greenberg) writes:
>Our copy of Aztec C (the latest version, 3.6 I think) arrived a few days
>ago.  I spent a day trying to use it, then gave up and went back to MPW C
>(which, although incredibly slow at compilation, is a solid package which
>works).
>
> - You can't redirect the output of make when it is invoked from the
>   Aztec shell; eg:  make all >error.log
>   The redirection is ignored, and all of the error messages are sent to
>   the console, and scroll off the top of the screen before you can read
>   them.

Now just what were you trying to do? The output of make normally does NOT 
go to the screen. The ERROR output does. Try redirecting the error output
to a file; you will find it does what you want it to do. You'll find info
about how to do it in the SHELL chapter of the manual. It really does help
to read the manual :-). A lot of problems could be avoided if people did!

> - If my screen saver (Moire) kicks in, then the Aztec shell cannot
>   redraw the screen, and often crashes the system.

That is because the screen data is not buffered. They really should rewrite
the screen package. On the other hand, this sounds like a good task to
learn the package.

>I finally decided that, if I had this much trouble just trying to
>compile a program, then the compiler itself is probably not to be
>trusted either.  Has anyone else had these problems, or discovered
>a solution?

Interesting. I have found the compiler to be amazingly good. Except for
the problem with pointers to pascal functions being always allocated in
global memory, it seems to be fine! It also allows me to directly look at
the output of the compiler so that I can optimize the C code when I 
write it (Since there are several ways to code something, I prefer to
find the fastest and most efficient. This is a pain to find in LSC or MPW).
I really don't believe a day is enough time to test out any software. 

Try again. We use both MPW & Aztec. They both are good packages and have
their places. I really doubt that you liked MPW the first time you tried it.
Especially if you were used to programming on a UNIX machine. After all, its
make is not even close to the "real" make.
Good luck,
Jack Brindle