Re: RFC: Making T_FUNCTION optional in method declarations
| From: | Patrick ALLAERT | Date: | Thu, 02 Dec 2010 09:34:33 +0000 |
| Subject: | Re: RFC: Making T_FUNCTION optional in method declarations | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50801@lists.php.net to get a copy of this message | ||
2010/11/30 Kalle Sommer Nielsen <kalle@php.net>:
> Hi
>
> 2010/11/30 Patrick ALLAERT <patrickallaert@php.net>:
>> With this patch, something looks inconsistent to me:
>> Both properties and methods have a visibility
>> (public|protected|private) and a keyword: "var" (T_VAR) and "function"
>> (T_FUNCTION) respectively.
>> However "private var $foo;" generates a fatal error but "private
>> function foo(){}" not?
>
> The "var" keyword is an alias of the "public" keyword for BC with
> PHP4. So it would be illogically to declare a property both private
> and public at the same time ;-)
Shouldn't we get rid of that kind of pre-PHP5 stuff _before_
introducing the possible omission of T_FUNCTION?
Patrick