Re: FSCatalogInfo randomness
Re: FSCatalogInfo randomness
- Subject: Re: FSCatalogInfo randomness
- From: "Finlay Dobbie" <email@hidden>
- Date: Tue, 30 Oct 2007 14:45:47 +0000
On 30/10/2007, Alastair Houghton <email@hidden> wrote:
> On 30 Oct 2007, at 14:27, Uli Kusterer wrote:
>
> > What about checking the return values of these functions? Probably
> > one of them is returning some error that you aren't aware of, and
> > isHidden is then set based on arbitrary data in an un-initialized
> > FSCatalogInfo struct.
> >
> > See <http://www.zathras.de/blog-carbon-for-the-cocoa-guy-
> > oserror.htm> for a description of how to interpret the return values
> > from FSGetCatalogInfo, FSPathMakeRef and LSCopyItemInfoForURL.
>
> It isn't strictly speaking a Cocoa question, but---since you bring
> that up---is there a function anywhere that will convert a Carbon
> error number into a meaningful (NS-)string? Or a database, perhaps,
> of OSStatus return codes? It'd be really handy to be able to look
> them up quickly without playing the hunting-about-in-the-system-
> headers game.
In theory, this is what NSError/CFError are for. In practice, there
isn't really any way of doing it other than grepping the headers at
the moment. There used to be a little utility on classic for doing it,
I forget the name.
-- Finlay
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden