Re: RFC: Making T_FUNCTION optional in method declarations

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 ;-) -- regards, Kalle Sommer Nielsen kalle@php.net