Re: RFC: Making T_FUNCTION optional in method declarations

I toast to that. Get rid of T_VAR already. Regards, David On Thu, Dec 2, 2010 at 3:34 AM, Patrick ALLAERT <patrickallaert@php.net>wrote: > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >