Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50636
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: Pierre Joye <pierre.php@gmail.com>
Cc: Pierrick Charron <pierrick@webstart.fr>, PHP internals list
 <internals@lists.php.net>
In-Reply-To: <AANLkTikVexGwOe2Yktn7y2pqfVgGpVOsv+Ekfu72tTu=@mail.gmail.com>
References: <1290879624.7033.826.camel@guybrush>
	 <AANLkTinBkG5560r0tkqqwXkUyCt-HkC74MXNQAJmsPyd@mail.gmail.com>
	 <AANLkTikVexGwOe2Yktn7y2pqfVgGpVOsv+Ekfu72tTu=@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 27 Nov 2010 19:40:59 +0100
Message-ID: <1290883259.7033.830.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method
 declarations
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Sat, 2010-11-27 at 19:30 +0100, Pierre Joye wrote:
> +1 if "While technically possible this RFC suggests that the following
> shall NOT be valid for keeping the code readable " also means that the
> patch implements it as well (force the function visibility property
> usage).

The patch follows the RFC's suggestion. This option is mentioned to make
it clear that this is a expected limitation if implemented. (And to
allow other opinions, which I don't expect)

johannes