Re: NSFileWrapper Role
Re: NSFileWrapper Role
- Subject: Re: NSFileWrapper Role
- From: Mike Abdullah <email@hidden>
- Date: Sat, 25 Feb 2012 12:54:40 +0000
As an added advantage on top of that it can avoid loading existing files into memory until needed. This is particularly handy when writing document packages as those files can be written quickly as hard links, rather than loading into memory and writing out afresh.
Sent from my iPad
On 25 Feb 2012, at 12:27 PM, Graham Cox <email@hidden> wrote:
>
> On 25/02/2012, at 2:47 PM, -Sergei G- wrote:
>
>> I don't quite get the role of NSFileWrapper. It appears to provide a subset of NSFileManager functionality. Some of the Apple samples use NSFileWrapper to implement bundle support, but it is not clear if that's a requirement or just a choice of the developer.
>>
>> Can someone elaborate beyond the official
>> The NSFileWrapper class provides access to the attributes and contents of file-system nodes. A file-system node is a file, directory, or symbolic link. Instances of this class are known as file wrappers.
>
>
> It allows you to represent a file that doesn't yet exist, even if it has a complex structure. You can construct its contents at your leisure, then, it can be written to a real file in one go.
>
> --Graham
>
>
>
> _______________________________________________
>
> 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
_______________________________________________
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