Re: Cocoa stripping resource forks: does Jaguar fix?
Re: Cocoa stripping resource forks: does Jaguar fix?
- Subject: Re: Cocoa stripping resource forks: does Jaguar fix?
- From: Pierre-Olivier Latour <email@hidden>
- Date: Thu, 04 Jul 2002 21:14:48 +0200
>
> ...It wouldn't be much work
>
> for Apple to fix in the underlying Cocoa API and you won't even have to
>
> touch your code.
>
>
Don't think so. What about things like this
>
>
-(void)copyFile:(NSString*)a to:(NSString*)b {
>
NSData *d=[d dataWithContentsOfFile:a];
>
[d writeToFile:b atomically:NO];
>
}
>
>
Agreed that it is and always was suboptimal, but it is and always was a
>
perfectly valid OpenStep / Cocoa code.
You're voluntarily taking a exaggerated example! I can also write:
-(void)copyFile:(NSString*)a to:(NSString*)b {
NSData *d=[d dataWithContentsOfFile:a];
[d writeToFile:b atomically:NO];
}
And pass it a path to a bundle and it won't work. Oohh... Bad. Let's drop
Bundles then since Cocoa cannot handle them properly :->
Once again, we're not talking about creating resource files with Cocoa, only
not destroying them when moving, reading, copying using standard API calls
_made for_ this purpose, not custom file routines you may write.
However, I join the opinion of the starter of thread posted earlier, and
stop speaking about all of this right now.
_____________________________________________________________
Pierre-Olivier Latour email@hidden
Manager and Lead Programmer
French Touch software
http://www.french-touch.net
Cool source code:
http://www.french-touch.net/CodeWareHouse
_______________________________________________
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.