Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50635
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <B6.E1.14730.A8F41FC4@pb1.pair.com>
To: internals@lists.php.net
References: <1290879624.7033.826.camel@guybrush>
In-Reply-To: <1290879624.7033.826.camel@guybrush>
Date: Sat, 27 Nov 2010 18:35:40 -0000
Lines: 1
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="utf-8";
	reply-type=original
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: RFC: Making T_FUNCTION optional in method declarations
From: ross@php.net ("Ross Masters")

﻿+1, has crossed my mind before =)

"Johannes "Schlüter""  wrote in message 
news:1290879624.7033.826.camel@guybrush...

Hi,

every now and then while writing classes I forget to add the "function"
keyword between my visibility modifier and the method name in a class
declaration. I don't think it is required for readability and it is not
needed by the parser to prevent conflicts, I therefore propose the
following RFC incl. patch to allow writing

        class Foo {
            public bar() {
                echo "Hello World";
            }
        }

Without T_FUNCTION token. In my opinion an access modifier /public,
private protected, static, final) should still be required for keeping
readability.

RFC: http://wiki.php.net/rfc/optional-t-function
Patch: http://schlueters.de/~johannes/php/zend_optional_t_function.diff

johannes