Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50628
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 27 Nov 2010 18:40:23 +0100
Message-ID: <1290879624.7033.826.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC: Making T_FUNCTION optional in method declarations
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

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