Re: NSData question
Re: NSData question
- Subject: Re: NSData question
- From: Chris Kane <email@hidden>
- Date: Tue, 2 Apr 2002 18:05:31 -0800
I have trouble believing that method could be exactly what anybody is
looking for, unless you're implementing your own old-style binary plist
parser, which is nobody.
The cursor value going in should be the location (index) at which to
begin deserialization, and after the method returns will be the location
up to which the deserialization read. Note that bytes to be
"deserialized" are expected to be in serialized format. If you don't
know what that last means, they probably aren't.
Chris Kane
Cocoa Frameworks, Apple
On Tuesday, April 2, 2002, at 12:16 PM, Jason Moore wrote:
Hello. Can anyone help me with NSData's
deserializeBytes:length:atCursor: method? It's exactly what i've been
looking for, but i'm having trouble getting it to work.
- (void)deserializeBytes:(void *)buffer length:(unsigned)bytes
atCursor:(unsigned *)cursor
i have a char* array i'm using for the 'buffer' argument, and an
unsigned int for 'bytes', but i'm not sure exactly how to do 'cursor'.
is it a pointer to an unsigned int? where should it start, the address
of the NSData objects' data or 0? The documentation is exceptionally
sparse for this one. Examples would be great. thanks again.
Jason
_______________________________________________
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.
_______________________________________________
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.