Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108061
To: internals@lists.php.net
References: <CAF+90c_PXAa8PSBzULa0WHViQ-XvuX+BuYQfx6c1zOf-9pOA=A@mail.gmail.com>
Message-ID: <e64fe4bd-4cbf-0528-6505-0b57fe9afea6@ralphschindler.com>
Date: Thu, 9 Jan 2020 08:27:36 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0)
 Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <CAF+90c_PXAa8PSBzULa0WHViQ-XvuX+BuYQfx6c1zOf-9pOA=A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Allow ::class on objects
From: ralph@ralphschindler.com (Ralph Schindler)


> 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?

     $fooAnon = new class extends Foo {};
     echo $fooAnon::class; // TypeError or class@anonymous?

There's prob a few more edge cases, but this is a start.

-ralph