Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60093
Return-Path: <nicolas.grekas@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 35995 invoked from network); 17 Apr 2012 18:46:12 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 17 Apr 2012 18:46:12 -0000
Authentication-Results: pb1.pair.com header.from=nicolas.grekas@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=nicolas.grekas@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
X-PHP-List-Original-Sender: nicolas.grekas@gmail.com
X-Host-Fingerprint: 209.85.215.42 mail-lpp01m010-f42.google.com  
Received: from [209.85.215.42] ([209.85.215.42:36323] helo=mail-lpp01m010-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 71/1C-03996-47ABD8F4 for <internals@lists.php.net>; Tue, 17 Apr 2012 14:46:12 -0400
Received: by lahl5 with SMTP id l5so5182392lah.29
        for <internals@lists.php.net>; Tue, 17 Apr 2012 11:46:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        bh=94ujQqjWH6G1dOj8wjObL+O7JUB+WTonh53HBtKK9Is=;
        b=cSV1T3e7e9gjW+JBuJedix/a8JUR7DIB2qRP0HyQkx9Sj1A/Gd4mlqRo4cJA6kdLOv
         H0pUIUMI5EVwJ+18cimbXN2mf23qmoka0dHZyynUDbKsn2cb3J5B7T04pWF7T6Mzi8Jo
         PzvCjRcpg0g5XruZBeRK0YOMA+LbdkclIpZTUqmbDhdZiTwAZSUKX6NyGyL7YE87KPP/
         fJzBc/YgVVBIdJnMa82+YP4b9CyOSyKX3mhDvaAy31s648WQpme15C8z0Jazt+NBSVPx
         rgSTC+i8fhlyGCqMSt0PKB8rJ6L7PL0cp06wBQ4TXuVsm1kN5+qqfzm4m1SFcU+Ffu40
         pC8g==
Received: by 10.152.133.144 with SMTP id pc16mr15291742lab.0.1334688369299;
 Tue, 17 Apr 2012 11:46:09 -0700 (PDT)
MIME-Version: 1.0
Sender: nicolas.grekas@gmail.com
Received: by 10.152.13.34 with HTTP; Tue, 17 Apr 2012 11:45:48 -0700 (PDT)
In-Reply-To: <CAF+90c-UPEV5cV+LtPa9ROi_mvUcmgUrD4Og1JSj_-FSCUqpug@mail.gmail.com>
References: <4F89D4F1.8070009@ralphschindler.com> <4F8CEB3B.4080702@ralphschindler.com>
 <CAOWwgp=Bm2fmoAy9p_5VAeGGTYd61=4ooQL8+Fg2RQt+mySQPg@mail.gmail.com>
 <4F8DA14F.1030204@sugarcrm.com> <CAF+90c-UPEV5cV+LtPa9ROi_mvUcmgUrD4Og1JSj_-FSCUqpug@mail.gmail.com>
Date: Tue, 17 Apr 2012 20:45:48 +0200
X-Google-Sender-Auth: 89QdFEtWRvsdZgq34j-5Y9M-WtQ
Message-ID: <CAOWwgp=NNOpdKegt9QfsMM2p92+RXhXRV+tRAp1vWvZF67g-RA@mail.gmail.com>
To: "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: nicolas.grekas+php@gmail.com (Nicolas Grekas)

> From the collisions point of view `class` and `__CLASS__` are equally
> safe.

> Imho ClassName::class reads nicer and also looks similar to the
> similar ClassName.class syntax in Java.

The current __CLASS__ could then be written self::class. Looks more
"namespace/object oriented", where __CLASS__ feels procedural?

How would static::class behave ? is it handled by the current patch?
Maybe the test case could be extended to reflect this, and also for
self::class?