Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucdavis!kongur!heberlei
From: heberlei@kongur.ucdavis.edu (Louis Todd Heberlein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Aztec C 3.6c problems
Keywords: Argghhh...
Message-ID: <6438@ucdavis.ucdavis.edu>
Date: 10 Jan 90 23:52:47 GMT
References: <685@cluster.cs.su.oz>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: heberlei@kongur.UUCP (Louis Todd Heberlein)
Organization: U C Davis, Dept. of Electrical Engineering and Computer Science
Lines: 32

My e-mail bounced, so I am posting this.  Bandwidth gods, please
forgive me.

In article <685@cluster.cs.su.oz> johnz@cluster.cs.su.oz (John Zic) writes:
>I am have found some problems with Aztec C + SDB, version 3.6.

[lots of problems]

>Is it me, or has anyone else had these problems?  I find using this compiler
>very frustrating, and I am starting to wish that I hadn't bought it.

I went through 3 versions of Aztec C (4 including an Amiga version)
before switching to another company.  However, I still find the Mac
frustrating to program: there is a lot of things to manage, you spend
a lot of time on the interface, it takes a while to learn how to
interact properly with the toolbox, and the operating system isn't
very forgiving (I have hit the old reboot switch a lot of times).  It
is a quantum leap going from programming on a sturdy UNIX and a simple
vt100 terminal to programming properly on a Mac, so you are not alone
in your frustrations.

>Please DON'T tell me that I should have bought LightSpeed C, or MPW C, or..
>I just want to know how I can fix these problems without spending more money.

Aztec used to have a phone number for technical questions, check your
manual or drop me a line if no one is able to help you.

>
>John Zic, Basser Dept of Computer Science, University of Sydney.

Todd Heberlein
heberlei@kongur.ucdavis.edu	128.120.57.118