Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69293 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2607 invoked from network); 23 Sep 2013 19:35:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2013 19:35:38 -0000 Authentication-Results: pb1.pair.com header.from=lars@strojny.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lars@strojny.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain strojny.net from 46.4.40.248 cause and error) X-PHP-List-Original-Sender: lars@strojny.net X-Host-Fingerprint: 46.4.40.248 milch.schokokeks.org Received: from [46.4.40.248] ([46.4.40.248:42819] helo=milch.schokokeks.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8E/92-25349-70890425 for ; Mon, 23 Sep 2013 15:35:36 -0400 Received: from lstrojnypro4.fritz.box (ppp-88-217-71-53.dynamic.mnet-online.de [::ffff:88.217.71.53]) (AUTH: PLAIN lars@schokokeks.org, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by milch.schokokeks.org with ESMTPSA; Mon, 23 Sep 2013 21:35:32 +0200 id 0000000000000026.0000000052409804.00007467 Content-Type: multipart/signed; boundary="Apple-Mail=_6F5C4AAB-1BEF-44FE-9D4E-FAE9A497C91D"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) In-Reply-To: <6D.71.03575.86970425@pb1.pair.com> Date: Mon, 23 Sep 2013 21:35:31 +0200 Cc: internals@lists.php.net Message-ID: References: <6D.71.03575.86970425@pb1.pair.com> To: Joe Watkins X-Mailer: Apple Mail (2.1510) Subject: Re: [PHP-DEV] RFC: Anonymous Classes From: lars@strojny.net (Lars Strojny) --Apple-Mail=_6F5C4AAB-1BEF-44FE-9D4E-FAE9A497C91D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Joe, Am 23.09.2013 um 19:22 schrieb Joe Watkins : [...] > As I have said, serialization does work, and unserialization does = work ... >=20 > 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. >=20 > 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 ... >=20 > 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 --Apple-Mail=_6F5C4AAB-1BEF-44FE-9D4E-FAE9A497C91D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIVAwUBUkCYAyQPF+sCY6wHAQKSSA//RGj/tFUcH+78ik0/dqCwOR2mqeXOncl9 GVmf7lVBXYw00TnnoEy8DGE3gSRPWrr2umCrnHDB95u72gQHCtcnC8rmXnFkpTcW PtcF7WhhWzy9h6dmkl0iG3mcwzXBdt7BCVSI9ykYFo9uENMgWmBe1n4el61G7FHv Mx0qMoIX6XmVYC8olcoFoIRdPSKGp62ZnLfQjhZqUI262/9x6PIRufIdqHwfIrru JvF9I4wtP6qdOcQGUQ4DpmjDqMbxtaj+UhMCw5WnXo80WLzq1LBndSstInncpCky APgiy8H6luW4QidXpMMIRboN7JshBtvYj4LnaVaE+RlaoG/J1dsCJ6WzhIARmqfD YArv+mDhPplEz9a6Gi+xAdqW9q5Py4VN6Tk8BN/lMb+i17Rk05nP0cqooYVZ0SLT G+Kdpg9rRnhn69wZiRb5SGbP5ZuUSpimWazqvg0nrs3iKuiSZzN/s0Yo4c9ECMZm 5Y68d76UQHv3uplWIigYi9SX1yyOu+wFMzEA6Bly9ZZbg+bkUZcNdQv5KLUcNZmS Q7k1HZjL60yOsdvZt7j69fRQWSGEqP1iCMJ12MZ064uhOnvh66DIiaWHzWArjfcJ pkB4OTPZVdROhZJoNsd4QqGw+W1cOTutEk5Z3XgfyJhGd4wI7fwEnROnMm0piZ0g ynmAw2gL5AE= =Zge1 -----END PGP SIGNATURE----- --Apple-Mail=_6F5C4AAB-1BEF-44FE-9D4E-FAE9A497C91D--