Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86176
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <55524B3A.1090302@gmx.de>
References: <CAEYWF=6njoRpCAA=HsFj0bBTEdBnzDr+Qo3sypPtbLRXjVi5mA@mail.gmail.com>
	<55524B3A.1090302@gmx.de>
Date: Tue, 12 May 2015 15:05:14 -0400
Message-ID: <CAEYWF=4mt5CXJ224fFk2gz6WxbiVMyabxaRV3pUGgBJSDsVkQA@mail.gmail.com>
To: Christoph Becker <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3bb30adbe110515e72c17
Subject: Re: Static method call with single colon results in fatal error, not
 aparse error?
From: bishop@php.net (Bishop Bettini)

--001a11c3bb30adbe110515e72c17
Content-Type: text/plain; charset=UTF-8

On Tue, May 12, 2015 at 2:49 PM, Christoph Becker <cmbecker69@gmx.de> wrote:

> Bishop Bettini wrote:
>
> > class Foo {
> >     public static function bar() { echo 'bar'; }
> > }
> > Foo:bar();
> >
> >
> > Note the single colon.  According to 3v4l <http://3v4l.org/Ot3Fk>...
>
>   Foo:bar();
>
> is the same as
>
>   Foo:
>       bar();
>
> so it is parsed as labelled statement, and as such is syntactically
> valid since PHP 5.3.
>

Ah, labels, right.  Thanks!

I will now go off and grumble that labels should mandate, rather than just
accept, block scope since it's easy to forget one half of Paamayim
Nekudotayim....

--001a11c3bb30adbe110515e72c17--