johnz@cluster.cs.su.oz (John Zic) (01/09/90)
I am have found some problems with Aztec C + SDB, version 3.6.
* printf is broken when linked with any of c32.lib, cld.lib, cld32.lib
(works fine with c.lib). Simple statements like: printf("hello\n"); refuses
to print.
* sizeof(int) = 0 if compiled with '+L' compiler option (which is supposed
to make ints equivalent to longs, except under Toolbox calls).
* IUDateString always returns a shortDate format, irrespective
of the format requested. Secs2Date returns the correct structure,
as does IUTimeString (can actually change it by changing the
control panel settings).
* sdb crashes with ID=02 when trying to debug programs (not MPW tools, since
sdb can't debug them!).
Configuration:
Mac512KE with 1 Meg dove expansion and SCSI Port
System 6.04, with MPW Shell 3.0 Beta 1
(No Finder - startup application is MPW Shell).
'AppleShare Prep' AppleShare
INITS are:
'512KE XPRAM INIT' AutoBlack SFScrollInit
CDEVs are:
General Keyboard Mouse Sound
International Map
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.
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.
John Zic, Basser Dept of Computer Science, University of Sydney.heberlei@kongur.ucdavis.edu (Louis Todd Heberlein) (01/11/90)
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