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: Ondra Cada <email@hidden>
- Date: Thu, 4 Jul 2002 14:46:23 +0200
On Thursday, July 4, 2002, at 04:50 , Rosyna wrote:
The point is, whether you like the data or not, do *not* destroy *any*
kind of data.
You still don't (want to?) understand.
If you are writing a new app especially for Mac, you can use Carbon (or
the strange naming convention) to access forks; if you are writing a new
shell script especially for Mac, you can use CpMac. That is quite
irrelevant though.
The point is that there are billions and billions of code lines -- be it
Cocoa (written in OpenStep in those days when Macs still ran OS<9), plain
C (BSD, posix, ANSI), or shell scripts -- which were *NEVER* written with
forked files in mind, for the precious reason that they were written by
people who presumably never even heard of something alike. Thanks to OSX,
we (at last!) can use this huge code base.
There's a price though: this code does not, and never could, of course,
support all those Mac proprietary tricks. In other words, it is relatively
unimportant whether your or mine applications would preserve resource
forks or not, since ALWAYS there will be some ported code which would not,
and therefore using resource forks is and always will be inherently
unsafe (well, unless you stick with a very small number of carefully
tested applications).
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
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.