Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86390
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ralphschindler.com from 209.85.214.177 cause and error)
Message-ID: <556496B3.1030905@ralphschindler.com>
Date: Tue, 26 May 2015 10:52:19 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <55636034.6010003@mabe.berlin> <CAFMT4Nri34Ae-AdOxUY13La2QOC9OxbNGNce4X6ZRkYKNaeM-Q@mail.gmail.com>
In-Reply-To: <CAFMT4Nri34Ae-AdOxUY13La2QOC9OxbNGNce4X6ZRkYKNaeM-Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] ::class wrong case
From: ralph@ralphschindler.com (Ralph Schindler)



> <?php
>
> namespace foo;
>
> function bar(){}
>
> var_dump(bar::class); // string(7) "foo\bar"
>
> ?>
>
> This was not explained in the RFC at all, and had I known this I would
> have voted against it personally.

How would you suggest it be different, if not a "compile-time name 
expansion for classes"?

On a personal note, I've gotten plenty of benefit from the feature which 
(again, for me) totally eclipses the only very small regret that ::class 
looks like a class constant lookup.  That syntactical point could have 
gone either way, but I feel like the accepted syntax is still a good choice.

Your example above might attempt to cause some mis-direction to the 
reader of the code a bit because you have clearly defined a symbol 
(function) called "bar", yet you're still name-expanding a class called 
"bar", which technically could be living in the same namespace in a 
different file covered by an autoloader.  bar::class still does actually 
mean foo\bar the class, not the function.

<?php
namespace foo;
function bar() {}
class bar {}
var_dump(bar::class); // string(7) "foo\bar"
$b = new bar;
var_dump(get_class($b));

Thanks for your input,
-ralph