• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa stripping resource forks: does Jaguar fix?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa stripping resource forks: does Jaguar fix?


  • Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
  • From: Ondra Cada <email@hidden>
  • Date: Wed, 3 Jul 2002 18:31:29 +0200

On Wednesday, July 3, 2002, at 04:20 , Kirk Kerekes wrote:

How "portable" are file packages, anyway?

Totally, since they are just folders and nothing else.

How "portable" are ".rsrc" files?
How portable are colon-separated paths?

Not the slightest bit.

Yet Cocoa supports them all,

Just like many your other claims, wrong. There's (absolutely reasonably) no support in Cocoa to read the OS9-based rsrc contents; if you are unlucky enough to need to interpret those "resources", you have to go Carbon (or DIY via NSData/NSFileHandle plus knowledge of its internal format).

Again, just try eg. [NSString stringWithContentsOfFile:@":tmp:foo.bar"] (instead of /tmp/foo.bar) before claiming such ridiculous things as "Cocoa supports colon for path separator". The one standard path separator is slash, like it or not (actually I don't like it myself, should be some non-printable char IMHO; nevertheless it can't be changed anymore).

Forked files are a superset of flat files, so the ability to handle forked files does not affect the ability to handle flat files on systems which are limited to them.

Gee. The problem is that you are taking it from the opposite side. Of course that an API which supports forked files would support non-forked ones as well -- nobody argues that. The problem in this thread is quite different though: all the standard APIs (OpenStep -- aka Cocoa, BSD, posix,
ANSI, shell script, perl, PostScript, you-name-it) are designed for _NON-FORKED_ (or, rather, single-forked) files. Therefore, they can't support forked ones very well.

In other words: were we just now designing an OO API for Mac, it would be probably smart to design it multi-forked for compatibility with legacy OS9 things. We are not though -- we are using plethora of *existing*, *long-ago matured* APIs, none of which supports multi-forks. And that's it.
---
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.
  • Follow-Ups:
    • Re: Cocoa stripping resource forks: does Jaguar fix?
      • From: Dan Crevier <email@hidden>
    • Re: Cocoa stripping resource forks: does Jaguar fix?
      • From: Cameron Hayne <email@hidden>
    • Re: Cocoa stripping resource forks: does Jaguar fix?
      • From: Finlay Dobbie <email@hidden>
References: 
 >Re: Cocoa stripping resource forks: does Jaguar fix? (From: Kirk Kerekes <email@hidden>)

  • Prev by Date: Re: extracting html from text file
  • Next by Date: Re: Cocoa stripping resource forks: does Jaguar fix?
  • Previous by thread: Re: Cocoa stripping resource forks: does Jaguar fix?
  • Next by thread: Re: Cocoa stripping resource forks: does Jaguar fix?
  • Index(es):
    • Date
    • Thread