Re: RFC: Making T_FUNCTION optional in method declarations

Hi, first time on the lists, guess I'm from userlando too, +1 for readability, all I ever really look at are "( ... ){" at the end of the line so I personally don't think it affects readability. Also, this is the way its done in other languages and I have always found the function keyword unnecessary in PHP. Regards, David 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 ;-) > > > > -- > regards, > > Kalle Sommer Nielsen > kalle@php.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >