Re: NSFileManager
Re: NSFileManager
- Subject: Re: NSFileManager
- From: jgo <email@hidden>
- Date: Fri, 29 Jun 2001 11:58:11 -0700
>
Jonathan Stimmel <email@hidden> Sun, 2001-06-24 13:47:50 -0700
>
> On Sun, 2001 Jun 24 at 13:10:36 -0700, Tommy Braas wrote:
>
> Although it might not be a programmatic but it is definitely
>
> a documentation bug. I think it should clearly state under
>
> which circumstances [ NSFileManager currentDirectoryPath ]
>
> returns what.
>
>
>
> Am I the only one that thinks that?
>
>
How would you clarify this method? The method itself doesn't set the
>
current working directory, it's inherited from the process/application
>
that launched your application. You could document the finder's behavior,
>
but what if your program is launched from another location? What if the
>
finder's behavior changes in a future release (not likely, admittedly)?
>
What if (as already pointed out) someone starts your app from the command
>
line, where the cwd could be anywhere on the filesystem?...
Exactly. This needs to be documented. It's part of the API of
this method that it returns different information depending on
the context (duh, of course, since it is an important aspect of
context that it is reporting), that it is dependent on the behavior
of other objects and that their behavior may change, & even that
it may depend on the behavior of different objects in the future,
if that is likely. This is information required to make good use
of it. It shouldn't be swept under the opaque or ambiguous rug,
but made public and explicit. Yes, even if it requires a few
screen pictures, diagrams and several pages of non-formulaic text.
John G. Otto Nisus Software, Engineering
www.infoclick.com www.mathhelp.com www.nisus.com software4usa.com
EasyAlarms PowerSleuth NisusEMail NisusWriter MailKeeper QUED/M
Will program Macs for food.