Re: NSFileManager Help
Re: NSFileManager Help
- Subject: Re: NSFileManager Help
- From: Jason Coco <email@hidden>
- Date: Wed, 27 Aug 2008 21:39:18 -0400
On Aug 27, 2008, at 21:19 , J. Todd Slack wrote:
Hi Jason
-(BOOL)createDirectoryAtPath:(NSString*)path
withIntermediateDirectories:(BOOL)createIntermediates attributes:
(NSDictionary*)attributes error:(NSError**)error;
I saw this, but if I have to deploy on 10.4, will this call fail
on 10.4 since it is new in 10.5?
No, it won't. You could check programmatically for 10.5 and call it
(at least then, if it fails on 10.5 you will know why) and fall
back to the other call on 10.4.
I was thinking about this, but I dont quite get what #if I would
use. I know there is #if (MAC_OS_X_VERSION_10_3) as example, but
would I have to check like min MAC_OS_X_VERSION_10_4 max
MAC_OS_X_VERSION_10_4_11 (Where there .11 releases or .6?) and then
another conditional of greater MAC_OS_X_VERSION_10_5?
You wouldn't really have to do this. Just compile with the 10.5 SDK on
Leopard but set your deployment target for 10.4. Then call
respondsToSelector to see if the NSFileManager that you're using can
respond to the newer call. If not, use the older call. You don't need
any #ifdef's or anything like that. Take a look at this document:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/Introduction/chapter_1_section_1.html#/
/apple_ref/doc/uid/10000163-BCICHGIE
/jason
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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