Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comp.vuw.ac.nz!am.dsir.govt.nz!tui.marcam.dsir.govt.nz!tony
From: tony@tui.marcam.dsir.govt.nz (Tony Cooper)
Newsgroups: comp.unix.aux
Subject: Re: Definite bug in A/UX 2.0.1 SF Package
Message-ID: <1991Jun13.142039.8335@am.dsir.govt.nz>
Date: 13 Jun 91 14:20:39 GMT
References: <1991May26.110152.27421@am.dsir.govt.nz> <3104@redstar.cs.qmw.ac.uk> <13673@goofy.Apple.COM> <2#A-BQ@smurf.sub.org>
Sender: news@am.dsir.govt.nz
Reply-To: sramtrc@albert.dsir.govt.nz
Organization: Applied Mathematics Group D.S.I.R.
Lines: 26

The only bugs involved here are the moths in my brain. I reported a bug
where the SF C routines (ie the lowercase-named routines such as sfgetfile)
required sfgetfile(&where, ...) instead of sfgetfile(where, ...). Well this
is not a bug at all. It is supposed to be that way and is clearly documented
in the A/UX toolbox guides (both 1.1 and 2.0). My problem was that I thought
the lowercase routines were just for using C strings (instead of Pascal) and I
completely forgot that Points were different as well. I don't know why 
points are treated differently since both points and pointers to points
are 4 byte quantities, but I'm not much of a MacOS programmer so I don't
have a very good grasp of this stuff anyway.

And I mentioned in an earlier posting that sfgetfile crashed the system
when run under A/UX and compiled with cc. Well I don't know what caused
the crash but I do know that I can avoid it if I call WaitNextEvent three
times before sfgetfile (or SFGetFile or ...) then the crash doesn't
occur.

Cheers,
Tony Cooper

PS The newly announced hybrid programming environment looks pretty good.
Bit beyond my price range (cc is "free" and I use THINK C on the other side)
especially considering that A/UX currently has X11R4 programming tools and
a C compiler that compiles MacOS source already. It's hard to see what you
get extra for the money.
the ANSI compiler gets included "free" in future upgrades of A/UX.