Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69285
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <000901ceb86e$10be3fa0$323abee0$@net>
References: <D9.10.12097.032EF325@pb1.pair.com> <CFD0FBAE-D609-4149-A4F6-3CD831EE93D3@strojny.net>
 <52404AB9.2070007@php.net> <CAJ26g5Rua2G6bhn6hSWArrSZmEhZpuSsEL15FgAYbFi=_aMOiw@mail.gmail.com>
 <000901ceb86e$10be3fa0$323abee0$@net>
Date: Mon, 23 Sep 2013 09:39:15 -0700
Message-ID: <CADajX4Bq_zS+0mh+RMGgu3K9iRUDtcF__a6=EBTtPgAYTQPqfA@mail.gmail.com>
To: Chris Wright <daverandom@php.net>
Cc: Joe Watkins <krakjoe@php.net>, internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: Anonymous Classes
From: aharvey@php.net (Adam Harvey)

On 23 September 2013 08:03, Chris Wright <daverandom@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.