Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50713 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98756 invoked from network); 30 Nov 2010 08:52:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2010 08:52:11 -0000 X-Host-Fingerprint: 78.142.172.145 gate-g21.inqnet.at Received: from [78.142.172.145] ([78.142.172.145:26979] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/83-01713-A3BB4FC4 for ; Tue, 30 Nov 2010 03:52:10 -0500 Message-ID: To: internals@lists.php.net Date: Tue, 30 Nov 2010 09:52:07 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101028 Lanikai/3.1.6 MIME-Version: 1.0 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 X-Posted-By: 78.142.172.145 Subject: Re: RFC: Making T_FUNCTION optional in method declarations From: mike@php.net (Michael Wallner) On 11/27/2010 06:40 PM, Johannes Schlüter wrote: > Hi, > ... > 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 +1 for any PHP version. Insisting on keeping T_FUNCTION means advocating PHP to stay the odd anomaly in programming languages to me. Regards, Mike