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: Ondra Cada <email@hidden>
- Date: Thu, 4 Jul 2002 20:39:20 +0200
On Thursday, July 4, 2002, at 08:20 , Pierre-Olivier Latour wrote:
...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.
However, I'm wondering, do all file systems support extensions with more
than 3 characters or folder with extensions in their name?
Well, the only ones I bumped into which don't were those of CP/M, ATARI
TOS, MeSsy DOS, and Psion Epoc/16 (SIBO).
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
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.