Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59981
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: <4F8B766F.3000702@ralphschindler.com>
Date: Sun, 15 Apr 2012 20:31:27 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Simon Schick <simonsimcity@googlemail.com>
CC: internals <internals@lists.php.net>
References: <4F89D4F1.8070009@ralphschindler.com> <CAJWj5+EhPkmpWmAz4Yekh794SO4x4sM27VZLk-X9qsDzMP4aNg@mail.gmail.com>
In-Reply-To: <CAJWj5+EhPkmpWmAz4Yekh794SO4x4sM27VZLk-X9qsDzMP4aNg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Feature: Fully qualified class name resolution
 as scalar with class keyword
From: ralph@ralphschindler.com (Ralph Schindler)


> One thing I personally dislike in this implementation is the
> difference between CLASS and class ... One with and one without
> namespaces ...

I am not quite following.  There is no functional difference between 
"class", "CLASS", or "Class".  The parser is case insensitive with 
regards to keywords, which "class" or T_CLASS is on of.  The code 
snipped I showed there was from the .phpt test that I had included in 
the Zend/test code base to ensure it worked and did not break existing 
tests.

As per the namespaced and non-namespaced blocks, I was demonstrating how 
::class would resolve names regardless of if it were a FQCN or a short 
class name.  Effectively, you can put ::class behind any "type" name and 
it should work as demonstrated.

-ralph