Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50641
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain iki.fi designates 213.243.153.188 as permitted sender)
Message-ID: <4CF176B1.6050307@iki.fi>
Date: Sat, 27 Nov 2010 23:22:57 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= <johannes@schlueters.de>
CC: PHP internals list <internals@lists.php.net>
References: <1290879624.7033.826.camel@guybrush>
In-Reply-To: <1290879624.7033.826.camel@guybrush>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: jani.taskinen@iki.fi (Jani Taskinen)

+1 for PHP 7.0. :)

Stuff like this accumulating in trunk kinda makes it more and more 
something else than minor release..

--Jani


27.11.2010 19:40, Johannes Schlüter kirjoitti:
> 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
>
>
>