• 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: FSRef_fopen alternative
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSRef_fopen alternative


  • Subject: Re: FSRef_fopen alternative
  • From: Jerry <email@hidden>
  • Date: Tue, 15 Aug 2006 08:50:56 +0100


On 15 Aug 2006, at 08:42, Jens Ayton wrote:

mark:
Jens Ayton:
Edward K. Chew:

Well, that sounds like a straightforward way to go, but is it bullet-proof?

No, it isn't. However, fopen() is a path-based API; if you want to use
fopen() and related APIs, that's the cost. This is what happens when you
switch the underpinnings of an OS to modern super-duper robust Unix. :-/


But doesn't the carbon file manager sit on top of and use the unix APIs?

It is my understanding that the Carbon APIs work with a driver that
provides a different view of the file system, a directory structure
based on file/dirIDs rather than names or some such. This could well be
out of date or completely wrong; I haven't looked into it in depth.

This is described in QA1113: http://developer.apple.com/qa/qa2001/ qa1113.html


Jerry

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >FSRef_fopen alternative (From: "Edward K. Chew" <email@hidden>)
 >Re: FSRef_fopen alternative (From: Jerry <email@hidden>)
 >Re: FSRef_fopen alternative (From: "Edward K. Chew" <email@hidden>)
 >Re: FSRef_fopen alternative (From: Jens Ayton <email@hidden>)
 >Re: FSRef_fopen alternative (From: mark <email@hidden>)
 >Re: FSRef_fopen alternative (From: Jens Ayton <email@hidden>)

  • Prev by Date: Re: Xcode/gcc help in enforcing secure coding?
  • Next by Date: Re: FSRef_fopen alternative
  • Previous by thread: Re: FSRef_fopen alternative
  • Next by thread: Re: FSRef_fopen alternative
  • Index(es):
    • Date
    • Thread