Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69261
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <523FFE44.8030107@lerdorf.com>
References: <D9.10.12097.032EF325@pb1.pair.com> <523FFE44.8030107@lerdorf.com>
Date: Mon, 23 Sep 2013 10:44:47 +0200
Message-ID: <CALtuQzAXGiJaF7SvZkSNbk8NRsHd19m4LdBgbm0LicOUyskqUQ@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Joe Watkins <krakjoe@php.net>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1ba4ac2fe7404e7090ae4
Subject: Re: [PHP-DEV] RFC: Anonymous Classes
From: krebs.seb@gmail.com (Sebastian Krebs)

--001a11c1ba4ac2fe7404e7090ae4
Content-Type: text/plain; charset=ISO-8859-1

2013/9/23 Rasmus Lerdorf <rasmus@lerdorf.com>

> On 09/22/2013 11:39 PM, Joe Watkins wrote:
> >     https://wiki.php.net/rfc/anonymous_classes
> >
> >     I'd like to hear thoughts regarding the addition of anonymous
> > classes, patch included.
>
> I am having a hard time picturing a real-world use-case for this.
>

The use case is one-time usage of an "implementation", where you currently
probably pass callbacks into a "Callback*"-class like

    $x = new CallbackFoo(function() {
        /* do something */
    });

vs.

    $x = new Foo () {
        public function doSometing()
        {
            /* do something */
        }
    });

Imagine you have several abstract methods in one interface/class, which
would need several callbacks passed to the constructor.
Also '$this' is mapped to the right objects.

Regards,
Sebastian


>
> -Rasmus
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
github.com/KingCrunch

--001a11c1ba4ac2fe7404e7090ae4--