Re: Re: Re: Re: Re: Re: What is serializaton?
Re: Re: Re: Re: Re: Re: What is serializaton?
- Subject: Re: Re: Re: Re: Re: Re: What is serializaton?
- From: "Corey O'Connor" <email@hidden>
- Date: Mon, 24 Jul 2006 18:15:21 -0700
On 7/24/06, Michael Ash <email@hidden> wrote:
Writing initWithCoder: and encodeWithCoder: methods is trivial,
though, if slightly boring.
It might be "trivial", but you still have to do it and it does take
some thought to properly handle versioning. I read your post as
implying NSCoder did all the work for you. Which is why I disagreed.
I, for one, have no troubles with this stuff but I have had to train a
few BS CS grads in the proper way to serialize and deserialize. In
order for something to be "trivial" I believe the correct solution
needs to be obvious at first attempt. From what I've experienced
nobody produces a data marshaling scheme I'd consider "correct" at
first go. Functional, maybe, but perfect? Nah. Admittedly my
experience with data marshaling comes mostly from C/C++, not Cocoa.
Where does it state this? I looked around briefly and couldn't find
any such mention, and I'm curious to see what it has to say.
The note is at the bottom of:
http://developer.apple.com/documentation/Cocoa/Conceptual/Archiving/Concepts/objectgraphs.html#//apple_ref/doc/uid/20001293
I'd agree that no effective automated serialization scheme exists for
arbitrary data structures. Which is why I'd hope the one in the API
is deprecated. :-)
--
-Corey O'Connor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden