Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86174
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
Message-ID: <55524B3A.1090302@gmx.de>
Date: Tue, 12 May 2015 20:49:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: bishop@php.net, PHP internals <internals@lists.php.net>
References: <CAEYWF=6njoRpCAA=HsFj0bBTEdBnzDr+Qo3sypPtbLRXjVi5mA@mail.gmail.com>
In-Reply-To: <CAEYWF=6njoRpCAA=HsFj0bBTEdBnzDr+Qo3sypPtbLRXjVi5mA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Static method call with single colon results in fatal error,
 not aparse error?
From: cmbecker69@gmx.de (Christoph Becker)

Bishop Bettini wrote:

> class Foo {
>     public static function bar() { echo 'bar'; }
> }
> Foo:bar();
> 
> 
> Note the single colon.  According to 3v4l <http://3v4l.org/Ot3Fk>...
> 
> 5.2.17 and earlier:
> Parse error: syntax error, unexpected ':'
> 
> 5.3 and later, including 7 and HHVM:
> Fatal error: Call to undefined function bar()
> 
> 
> Is this really a run-time fatal error?  Unless I missed a memo, surely this
> should be a compile time error.

  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.

-- 
Christoph M. Becker