Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60188
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F8DFB17.7030509@sugarcrm.com>
References: <4F89D4F1.8070009@ralphschindler.com>
	<4F8CEB3B.4080702@ralphschindler.com>
	<CAOWwgp=Bm2fmoAy9p_5VAeGGTYd61=4ooQL8+Fg2RQt+mySQPg@mail.gmail.com>
	<4F8DA14F.1030204@sugarcrm.com>
	<B9.1A.03996.EF6AD8F4@pb1.pair.com>
	<4F8DCAC7.2050302@ralphschindler.com>
	<4F8DF2B6.4030709@sugarcrm.com>
	<CAF+90c961FHeB_R82WANe6dtn+3ZOXbgUAGjDO=hSSAFXy_OtQ@mail.gmail.com>
	<4F8DFB17.7030509@sugarcrm.com>
Date: Wed, 18 Apr 2012 15:01:41 +0200
Message-ID: <CAF+90c9nT7LJ-jwK5NrBmj3E4PkPNrHnET2uTr44Pqy2itakkw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: New Feature: Fully qualified class name resolution
 as scalar with class keyword
From: nikita.ppv@googlemail.com (Nikita Popov)

On Wed, Apr 18, 2012 at 1:21 AM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> Well, not that you mention it, I don't see a reason why we shouldn't
>> add run-time resolution where necessary. For once this would allow
>
> Runtime resolution of what? We already have get_class(),
> get_called_class() and __NAMESPACE__. Now, having constant expression
> for full class name might be useful since some contexts allow only
> constant expressions. But for runtime contexts we already have it. And
> there's no such thing as run-time resolution of namespaced class names.
Yes, you are right. static::class would be equivalent to
get_called_class() and $foo::class would be equivalent to
get_class($foo).

>> static::class, but also would allow $obj::class. Not sure this is
>> really necessary, but it would be more consistent :)
>
> $obj::class means "class" constant of the class whose name is given by
> string variable $obj. Probably not what you intended. And you have
> get_class() already.
As already mentioned, There can't be a class constant called "class",
because it is a keyword. (const class = 'Foo' is a syntax error).

But yes, I agree that runtime resolution only duplicates existing
behavior, so it isn't really necessary (you could argue thought that
self::class similarly also only replicates the existing __CLASS__). It
would be nice for consistency in my eyes, but I'm good without it too
:)

Nikita