Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60087
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F8DA14F.1030204@sugarcrm.com>
References: <4F89D4F1.8070009@ralphschindler.com>
	<4F8CEB3B.4080702@ralphschindler.com>
	<CAOWwgp=Bm2fmoAy9p_5VAeGGTYd61=4ooQL8+Fg2RQt+mySQPg@mail.gmail.com>
	<4F8DA14F.1030204@sugarcrm.com>
Date: Tue, 17 Apr 2012 19:07:46 +0200
Message-ID: <CAF+90c-UPEV5cV+LtPa9ROi_mvUcmgUrD4Og1JSj_-FSCUqpug@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Nicolas Grekas <nicolas.grekas+php@gmail.com>, 
	Ralph Schindler <ralph@ralphschindler.com>, 
	"internals@lists.php.net" <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 Tue, Apr 17, 2012 at 6:58 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> May I suggest using foo::__CLASS__ instead of foo::class ? It's longer, but
>> closer to what already exists for this semantic (class name as string),
>> don't you think ?
>
> I like this. __CLASS__ is already being used as class name, and little
> chance of colliding with some code since you're not supposed to be using
> __ prefix in your names.
From the collisions point of view `class` and `__CLASS__` are equally
safe. They both are lexer keywords, so it's not possible to declare
constants with them as name.

Imho ClassName::class reads nicer and also looks similar to the
similar ClassName.class syntax in Java.

Nikita