Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!keith
From: keith@Apple.COM (Keith Rollin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Standard File and Working directories...
Message-ID: <54413@apple.Apple.COM>
Date: 27 Jun 91 23:01:37 GMT
References: <1991Jun26.084825.9019@dartvax.dartmouth.edu> <54370@apple.Apple.COM> <1991Jun27.162709.14957@dhw68k.cts.com>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 29

In article <1991Jun27.162709.14957@dhw68k.cts.com> finnegan@dhw68k.cts.com (Greg Finnegan) writes:
>>There are only two reasons for creating working directories:
>>
>>- If you are launching another application that expects to find its
>>  location by making a GetVol call.
>>- If you are writing a hack that involves part of the system that
>>  still uses working directories. For example, one person was
>>  patching StdFile and needed to create WD's. Another person
>>  wanted to fake out INIT 31 and needed to create WD's.
>
>I can think of one more: if you are using someone else's commercial
>library which was written a few years ago and it requires a wdRefNum
>for some of its file calls (probably assuming the library would be
>called immediately after a Std File call).

This is a good and valid point. As a matter of fact, MacApp 2.0.1
suffers from this, too. There is at least one routine (MAOpenfile)
that requires a working directory ID.

All knowledge of working directories are being excised from
MacApp 3.0, except where it has to convert the WD it gets
back from StdFile.

-- 
------------------------------------------------------------------------------
Keith Rollin  ---  Apple Computer, Inc. 
INTERNET: keith@apple.com
    UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith
"But where the senses fail us, reason must step in."  - Galileo