Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!att!cbnewsk!ech
From: ech@cbnewsk.ATT.COM (ned.horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: filedata from SFGetFile
Message-ID: <1919@cbnewsk.ATT.COM>
Date: 24 Jan 90 17:20:41 GMT
References: <9821@hoptoad.uucp>
Organization: AT&T Bell Laboratories
Lines: 15

From article <9821@hoptoad.uucp>, by tim@hoptoad.uucp (Tim Maroney):
> You're making it awfully hard on yourself.  All you're grabbing from
> the file filter are the volume reference number and directory ID, which
> are stored in the low-memory globals SFSaveDisk and CurDirStore
> already.  Standard File tracks these as it goes from folder to folder
> and disk to disk...

Uh.  While things may work this way today, the only committment
Inside Mac makes is that those globals will be used to initialize the
SFGet/SFPut, and that they'll be set at completion of SFGet/SFPut.  There's
no good reason they should "track," and no guarantee that they'll always
do so.  That, quite aside from the general caveat to use lo-mem globals
as little as possible.  Using the file filter sounds prudent to me.

=Ned Horvath=