Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92473
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender)
To: internals@lists.php.net
References: <CAL=_i_==wsq5j2Jf1QdusxaCBU8COX3eJvZY+puD8zH1zCrTXw@mail.gmail.com>
 <CAF+90c_3Sj7zqJaQy6u=3RQOxh+Y7uZ7Eo-pW2m=Ty95npfjfA@mail.gmail.com>
Message-ID: <5716561C.3020600@gmail.com>
Date: Tue, 19 Apr 2016 17:00:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAF+90c_3Sj7zqJaQy6u=3RQOxh+Y7uZ7Eo-pW2m=Ty95npfjfA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Anonymous Class Lexical Scope
From: rowan.collins@gmail.com (Rowan Collins)

Hi Nikita,

I was thinking some more about your suggestion:

Nikita Popov wrote on 19/04/2016 15:18:
> $foo = 42;
> return new class {
>      private $bar = $foo;
>      public function getBar() { return $this->bar; }
> }

If we allowed this, would it make sense to also allow it in named 
classes? This is currently illegal [https://3v4l.org/Kp0ep]:

$foo = 42;
class X {
     private $bar = $foo;
     public function getBar() { return $this->bar; }
}

> It probably doesn't make sense to
> restrict this to specific expressions, so all of
>
> return new class {
>      private $a = $var;
>      private $b = $obj->prop;
>      private $d = $obj->prop ?? 'default';
>      // ...
> }
>
> could be fine.

We don't allow importing expressions into closures, nor are any of those 
property initialisations valid in the definitions of named classes, so I 
think allowing them here would be odd.

Regards,
-- 
Rowan Collins
[IMSoP]