Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108074
MIME-Version: 1.0
References: <CAF+90c_PXAa8PSBzULa0WHViQ-XvuX+BuYQfx6c1zOf-9pOA=A@mail.gmail.com>
 <e64fe4bd-4cbf-0528-6505-0b57fe9afea6@ralphschindler.com>
In-Reply-To: <e64fe4bd-4cbf-0528-6505-0b57fe9afea6@ralphschindler.com>
Date: Thu, 9 Jan 2020 21:45:15 +0100
Message-ID: <CAF+90c8r2fNLcg4X4Xwf8-sbckMF-DP_T0hGdW34W23Ra1JRrw@mail.gmail.com>
To: Ralph Schindler <ralph@ralphschindler.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000f765b059bbb172d"
Subject: Re: [PHP-DEV] [RFC] Allow ::class on objects
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000000f765b059bbb172d
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 9, 2020 at 3:28 PM Ralph Schindler <ralph@ralphschindler.com>
wrote:

>
> > Another small RFC, to allow $object::class syntax:
> >
> > https://wiki.php.net/rfc/class_name_literal_on_object
>
> Hi Nikita,
>
> Glad to see enhancements to ::class. Open questions, given:
>
>
>      class Foo {}
>
>      $foo = new Foo;
>      echo $foo::class; // Foo
>

>      $fooClass = Foo::class;
>      echo $foo::class; // TypeError b/c string?
>

Yes, at least per the current proposal. Whether to allow this is listed as
an open question.


>      $fooAnon = new class extends Foo {};
>      echo $fooAnon::class; // TypeError or class@anonymous?


The same as get_class($fooAnon), which will be of the form
"class@anonymous\0SOME_PAYLOAD_HERE".
While the part after class@anonymous is cut of when printing in most
places, anonymous classes still do have a unique class name.

Nikita

--0000000000000f765b059bbb172d--