Re: RFC: Anonymous Classes

Hi Joe, Am 23.09.2013 um 19:22 schrieb Joe Watkins <krakjoe@php.net>: [...] > As I have said, serialization does work, and unserialization does work ... > > Classes do have unique names, so as long as the entry is present upon unserialize you will get > the object you expect ... if the entry is not present unserialization will fail silently. > > The same kind of thing can happen where you have declared a class based on some predicate, > whose value has changed upon unserialize and so the entry is not present ... > > I'm not sure it is necessary to force any particular behaviour for serialization, it > depends entirely on the application whether or not the entry is present upon serialization, it > should be left down to the programmer. it would make sense to forbid serializing anonymous classes like we forbid serializing closures. What do you think? cu, Lars

Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc