Re: Carbon vs Cocoa
Re: Carbon vs Cocoa
- Subject: Re: Carbon vs Cocoa
- From: Rosyna <email@hidden>
- Date: Wed, 2 Oct 2002 15:45:00 -0700
Using FSRefs is unacceptable for a lot of things. (Save and Revert is
ok though) since on UFS volumes they are not valid between
applications or application launches so they can't be communicated to
eachother. However, if you convert the FSRef to a POSIX path or an
Alias then pass it and convert it back to FSRef, all is well. So
ignore everything I just said in this email since it's completely
moot but I am too lazy to delete this message.
Ack, at 10/2/02, email@hidden said:
This could be fixed if methods using file paths as arguments
were deprecated like they were long ago with respect to the
Toolbox in Mac OS (circa System 7 IIRC). If one uses FSRefs
(for runtime) and Aliases (for non-volatile storage) instead this
problem would be fixed. Since 10.1 NSDocument behaves like
it uses an FSRef internally. FSRefs are available in
CoreFoundation, but curiously not in Foundation proper.
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
---
Please include any previous correspondence in replies, it helps me
remember what we were talking about. Thanks.
_______________________________________________
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.