Re: Philosophy of FSRef - way
Re: Philosophy of FSRef - way
- Subject: Re: Philosophy of FSRef - way
- From: Ruslan Zasukhin <email@hidden>
- Date: Thu, 10 Feb 2005 18:49:51 +0200
On 2/10/05 6:26 PM, "M. Uli Kusterer" <email@hidden> wrote:
> You're aware that FSRefs are, strictly spoken, a Carbon technology,
> and thus you'll probably get much better answers about this on
> Carbon-Dev.
>
> At 16:41 Uhr +0200 10.02.2005, Ruslan Zasukhin wrote:
>> 1) It looks very weird that I cannot create Fsref for non-existing object,
>> Like we was able do this with FSSpec. What a great idea is behind of this?
>
> The idea behind an FSRef is that it will stay valid even if your
> file is moved around or renamed (though not across restarts).
> Pathnames obviously don't work for this, and FSSpecs encode the
> parent directory's ID, and thus only stay valid if the folder
> *containing* your file is moved, but not if you take a file out of
> its folder.
I wonder where from you have get this info? :-)
In the Developer/Docs folder I have not see such texts
--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: email@hidden
web: http://www.paradigmasoft.com
To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden