Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69264
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.179 as permitted sender)
MIME-Version: 1.0
Sender: mike.php.net@gmail.com
In-Reply-To: <523FFE44.8030107@lerdorf.com>
References: <D9.10.12097.032EF325@pb1.pair.com>
	<523FFE44.8030107@lerdorf.com>
Date: Mon, 23 Sep 2013 11:00:43 +0200
Message-ID: <CALJZF3hRmc3_jS==WT+8_MDymGQmKpWJ5vTLUaAnTU71okzgCw@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Joe Watkins <krakjoe@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] RFC: Anonymous Classes
From: mike@php.net (Michael Wallner)

On 23 September 2013 10:39, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> 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.

It is a widely used pattern in object oriented programming:

$subject->attach(new class implements SplObserver {
  function update(SplSubject $s) {
    printf("Got update from: %s\n" $subject);
  }
);


I'd rather go for a `new BaseType` syntax, though:

$subject->attach(new SplObserver() {
  function update(SplSubject $s) {
    printf("Got update from: %s\n" $subject);
  }
);



-- 
Regards,
Mike