Talk:Object serialization

From Rosetta Code
Revision as of 20:25, 2 September 2009 by Rdm (talk | contribs) (Created page with 'Serializing object instances which have no state does not seem very meaningful. You could trivially satisfy this task in some languages merely by naming the objects. Meanwhile,…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Serializing object instances which have no state does not seem very meaningful. You could trivially satisfy this task in some languages merely by naming the objects.

Meanwhile, when I think about this issue, a variety of possibilities occur to me, for state. We could even introduce stateful classes and then [by implication] the classes would also need to be serialized -- but I do not think most of the examples do anything like this.

Can we update this task with a little bit of state? Perhaps, we can add a method which reports the time the object was first created? Or would that break all the existing implementations and thus be a bad idea?

Rdm 20:25, 2 September 2009 (UTC)