note
adrianh
<blockquote><em>The DESTROY problem is easy to get around...</em></blockquote>
<p>That just moves the problem from keeping DESTROY in sync, with keeping USED in sync :-)</p>
<blockquote><em> The serialization is a larger problem. I don't like the idea of everyone having to agree on a standard way of doing things to get the benefits of prior work. </em></blockquote>
<p>I'm not sure I follow this argument?</p>
<p>If you have a complex serialisation problem you'll be writing custom freeze/thaw methods anyway so it's not an issue.</p>
<p>If you're not - and basically want something that has all the attributes in it for you to Dump/freeze/thaw, then a base class would seem the best solution to put a generator for this sort of thing?</p>
<p>... or am I missing the point again... it is late...</p>
219728
219810