Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50828
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
Message-ID: <4CF7C944.8000909@daylessday.org>
Date: Thu, 02 Dec 2010 19:28:52 +0300
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101026 SUSE/3.0.10 Thunderbird/3.0.10
MIME-Version: 1.0
To: 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
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: tony@daylessday.org (Antony Dovgal)

-1

On 11/27/2010 08:40 PM, Johannes Schlüter wrote:
> 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
> 
> 
> 


-- 
Wbr,
Antony Dovgal
---
http://pinba.org - realtime statistics for PHP