🚀 go-pugleaf

In article <6462@dartvax.UUCP) earleh@dartvax.UUCP (Earle R. Horton) writes:
)I agree!  Byte the bullet, programmers!  Use PBOpen, PBRead, PBWrite, and
)the entire ensemble of IN ROM Macintosh file handling routines to make
)your code more efficient and also more able to withstand the effects of
)system upgrades.  You don't have to call SetVol(), you don't have to 

It gives you something else, too. I wrote fpack for the Mac a year or so ago.
One condition that is very hard to detect with portable C is "DISK FULL"!
Corrupted output files galore...

How did I fix it? The very unelegant way of calling the ROM to find out how
much space I had left before I opened a file for writing, and keeping track
of how much I wrote. It worked, but I ain't proud of it.

fpack 3.x will come out one of these days, as will par/unpar. Both will use
the infinitely more responsive (i.e. PBWrite says "Disk Full", not "I just
wrote an 'a'") ROM IO calls.

By the way, it has come to my attention, through a friend, that fpack
is still circulating in the PD world, and that the copy he got (on his Jasmine)
didn't work. The copy on his Jasmine was version 2.0. I don't have the records
to show when the change came about, but version 2.2 is the earliest version
I can confirm was compiled with a version of Mac C which knows about HFS.

I believe the differences between 2.0, 2.1 and 2.2 are the compiler changes
and the version number resources.

Version 2.2 works on my Dataframe XP20.

Does anyone still care?
-- 
+      Jim Budler      Advanced Micro Devices, Inc.      (408) 749-5806      +
+  Compuserve: 72415,1200; Delphi: JIMBUDLER;  Usenet: jimb@amdcad.AMD.COM   +