Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60107
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ralphschindler.com from 209.85.214.170 cause and error)
Message-ID: <4F8DCAC7.2050302@ralphschindler.com>
Date: Tue, 17 Apr 2012 14:55:51 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: internals@lists.php.net
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>
In-Reply-To: <B9.1A.03996.EF6AD8F4@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: New Feature: Fully qualified class name resolution
 as scalar with class keyword
From: ralph@ralphschindler.com (Ralph Schindler)

> "class" won't collide anyways, as it's already a keyword, and you can't use it
> in your constant or function names. __CLASS__ has bad connotations for me, as it
> resolves to the declaring class normally, not the class invoked.

I tend to agree.  __CLASS__ to me belongs to the family of constants 
like __DIR__ and __FILE__ where they are meant to be evaluated in-place 
and are simply a substitution for something completely static.

In my mind, while Foo::class returns a scalar, it is subject to 
resolution by use statements generally at the top of a file or namespace 
declaration and is computed based on what namespace it is in and what 
use statements affect it.

-ralph