Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69297
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CADq_CxpKv=mfme8iR3bwUO6mfnnjN0xDkAJ6=6cven3354rJPg@mail.gmail.com>
References: <D9.10.12097.032EF325@pb1.pair.com> <6D.71.03575.86970425@pb1.pair.com>
 <CADq_CxpKv=mfme8iR3bwUO6mfnnjN0xDkAJ6=6cven3354rJPg@mail.gmail.com>
Date: Mon, 23 Sep 2013 22:16:08 +0200
Message-ID: <CALtuQzC=N6Z6KPO5KnKc4-RSRjTCM0yTrXQC6mLFPFm9vQ8PtQ@mail.gmail.com>
To: "Kingsquare.nl - Robin Speekenbrink" <robin@kingsquare.nl>
Cc: Joe Watkins <krakjoe@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec53f30ed29979904e712b3a1
Subject: Re: [PHP-DEV] Re: RFC: Anonymous Classes
From: krebs.seb@gmail.com (Sebastian Krebs)

--bcaec53f30ed29979904e712b3a1
Content-Type: text/plain; charset=ISO-8859-1

2013/9/23 Kingsquare.nl - Robin Speekenbrink <robin@kingsquare.nl>

> Everyone,
>
> As a lurker i rarely have anthing to say, but this time i'd like to make an
> exception: I see some usability for this type of usage, but would like to
> disagree on the extra class...
> My usage would be more in line with JSON way of passing around objects...
> But i'd hate to see yet another new class type and kind of feel the
> StdClass would've been more logical...
>

To me it sounds like you mix something up and describe a different use case
(which is already easily possible)

$stdClass = (object) [
  'foo' => 'bar'
];

The RFC is about anonymous objects _with_ behaviour (-> methods), whereas
stdClass-objects doesn't have any methods.


> The reasons for this imho is that the StdClass is the one-for-all object
> without anything that's already there... (it's not like anonymous functions
> are something different than regular functions?)
>
> As for actual need: personally i can easily live without, but then again:
> we the influx of JSON-like notation / ubiquity this might make a logical
> follow up.. ?
>
> Met vriendelijke groet,
>
> Robin Speekenbrink
> Kingsquare BV
>
>
> 2013/9/23 Joe Watkins <krakjoe@php.net>
>
> > On 09/23/2013 07:39 AM, Joe Watkins wrote:
> >
> >> Morning All,
> >>
> >>      https://wiki.php.net/rfc/**anonymous_classes<
> https://wiki.php.net/rfc/anonymous_classes>
> >>
> >>      I'd like to hear thoughts regarding the addition of anonymous
> >> classes, patch included.
> >>
> >> Cheers
> >> Joe
> >>
> >
> > Serialization:
> >
> >   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.
> >
> >
> > Cheers
> > Joe
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>



-- 
github.com/KingCrunch

--bcaec53f30ed29979904e712b3a1--