Re: FSRefMakePath: error -35
Re: FSRefMakePath: error -35
- Subject: Re: FSRefMakePath: error -35
- From: Lawrence Sanbourne <email@hidden>
- Date: Sun, 23 Oct 2005 18:50:33 -0500
I just realized I can create the array like so:
CFArrayCreateMutable(kCFAllocatorDefault, 0, NULL);
The NULL is for CFArrayCallBacks. The function now works (yay!), but
did I introduce some terrible memory problem by using NULL for the
CFArrayCallBacks?
Thanks for memFullErr and all your help. Soon I'll post this and my
Cocoa wrapper.
Larry
On 10/23/05, Rosyna <email@hidden> wrote:
> It's fine to store them as paths. For the folders only. Otherwise
> you'd have to use memcpy and custom CFArray callbacks. Which is
> possible, but very tedious for just this kind of action.
>
> Also, for the malloc thing, return memFullErr (-108) if in bizarro
> world malloc returns NULL.
>
> Ack, at 10/23/05, Lawrence Sanbourne said:
>
> >On 10/23/05, Rosyna <email@hidden> wrote:
> >> // if the file is a folder, add it to an array.
> >
> >Stupid question: Is there a built-in collection in which one can store
> >FSRef pointers? CFArray doesn't seem to work, which is what I expected
> >anyway.
>
> --
>
>
> Sincerely,
> Rosyna Keller
> Technical Support/Holy Knight/Always needs a hug
>
> Unsanity: Unsane Tools for Insanely Great People
>
> It's either this, or imagining Phil Schiller in a thong.
>
--
Larry Sanbourne
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden