Re: Cocoa stripping resource forks: does Jaguar fix?
Re: Cocoa stripping resource forks: does Jaguar fix?
- Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
- From: Cameron Hayne <email@hidden>
- Date: Tue, 2 Jul 2002 18:31:04 -0400
On Tuesday, July 2, 2002, at 05:32 pm, Ondra Cada wrote:
BSD is a portable API. posix is portable API. The very same stands for
shell scripts. Cocoa should be a portable API, though Apple has messed
up OpenStep considerably.
While it would be nice if Cocoa were a portable API, I think that the
prime directive ought to be to support the Macintosh community of
developers and users.
Therefore, if a filesystem wants to work under it, *IT* has to support
what's needed -- not by dirty tricks like the special names, but by a
way which can be reconciled with the *STANDARD* techniques of BSD,
posix, shell scripts, OpenStep, whatever. If it does not, it's its
fault -- in this case, the blame is on the side of HFS+
From the point of view of the Macintosh community, HFS+ came before
Cocoa (it is irrelevant what the chronology was on some other systems),
and hence Cocoa needs to be compatible with HFS+.
... Cameron
--
Cameron Hayne (email@hidden)
Hayne of Tintagel
_______________________________________________
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.