Thanks Greg. Leaks filled!
-koko
On Oct 27, 2010, at 4:35 PM, Greg Guerin wrote:
koko wrote:
although I have implemented a different solution, just to note the
data fork (the file) does exist, it is nspath in the first line.
I don't see nspath being used to create a data-fork file in any code
you posted. It may be in the code you didn't post, or if I've
missed it, please point it out.
I also realize I wasn't clear. After the file exists, i.e. after
the file has been created WITHOUT a namedfork pathname, it's wrong
to use createFile on the resource fork. You can, however, open the
namedfork for writing. I have done this using C stdio (FILE*) and
it worked fine. Obviously, that's not one of the NSFileManager
functions.
Finally, the most recent code you posted is leaking the malloc'ed
buffer holding the resource-fork's bytes.
-- GG
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/koko%40highrolls.net
This email sent to k...@highrolls.net
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
