Re: Open Resource File with Cocoa Path
Re: Open Resource File with Cocoa Path
- Subject: Re: Open Resource File with Cocoa Path
- From: Andrew Mortensen <email@hidden>
- Date: Fri, 12 Apr 2002 10:19:26 -0400 (EDT)
You misunderstand my point. Once the path is compiled into one's
application, of course it can't be changed. The reason to use the
definition instead of the hard-coded path is that you can make a quick
recompile and have it work, instead of having to replace all hardcoded
entries to match the new path to the resource fork, *should Apple ever
change it in the header file*. Where'd you get the idea I meant it would
be updated in the old binary?
andrew
On Fri, 12 Apr 2002, Andrew Pinski wrote:
>
Apple cannot change it any more _PATH_RSRCFORKSPEC is a constant that is
>
stored in your app.
>
You should still use it because in the future you might forget what the
>
hack `/..namedfork/rsrc' was for.
>
>
Thanks,
>
Andrew Pinski
>
>
>
On Thursday, April 11, 2002, at 01:32 , Andrew Mortensen wrote:
>
>
> On Thu, 11 Apr 2002, Charles Srstka wrote:
>
>
>
>> I was told some time ago that it's better to use ..namedfork/rsrc than
>
>> /rsrc...
>
>
>
> This is correct. See sys/paths.h. _PATH_RSRCFORKSPEC is defined as
>
> "/..namedfork/rsrc". Use _PATH_RSRCFORKSPEC instead of the hardcoded
>
> path
>
> in case Apple changes it.
>
>
>
> andrew
>
_______________________________________________
>
cocoa-dev mailing list | email@hidden
>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.