On 23 September 2013 08:03, Chris Wright <daveran...@php.net> wrote: > To summarize how I think this should be handled: Serialisation results in a > stdClass, unserialisation cannot be done because if you want it you're > already > Doing It WrongT.
To me, serialising "successfully" would indicate that PHP could unserialise the object as it was. Since it can't, I'd prefer to just error out at the serialize() stage. As for the feature itself, I'm not really sold right now. The use cases I've seen for this previously in other languages have been situations where either a simple anonymous function or closure would suffice, or alternatively situations where you have a big anonymous class with lots of methods, and I think for the latter case I'd rather promote separating those sorts of implementations into standalone classes for readability reasons. Adam, who isn't even pretending that he's looked at the patch yet. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
