Re: [PHP-DEV] Re: RFC: Making T_FUNCTION optional in method declarations

2010-11-30 Thread Gwynne Raskind
On Nov 30, 2010, at 4:24 AM, Arvids Godjuks wrote: > Personally, as a user-land developer, I'm against it, so -1. > function keyword is the only sane way to quickly find a function > definition in lots of code. Not always IDE's are able to fully > understand the interconnections in frameworks and p

Re: [PHP-DEV] Re: RFC: Making T_FUNCTION optional in method declarations

2010-11-30 Thread Arvids Godjuks
Personally, as a user-land developer, I'm against it, so -1. function keyword is the only sane way to quickly find a function definition in lots of code. Not always IDE's are able to fully understand the interconnections in frameworks and point by CTRL + Click me to the function definition, not to

[PHP-DEV] Re: RFC: Making T_FUNCTION optional in method declarations

2010-11-30 Thread Michael Wallner
On 11/27/2010 06:40 PM, Johannes Schlüter wrote: Hi, ... Without T_FUNCTION token. In my opinion an access modifier /public, private protected, static, final) should still be required for keeping readability. RFC: http://wiki.php.net/rfc/optional-t-function Patch: http://schlueters.de/~johann

[PHP-DEV] Re: RFC: Making T_FUNCTION optional in method declarations

2010-11-27 Thread Ross Masters
+1, has crossed my mind before =) "Johannes "Schlüter"" wrote in message news:1290879624.7033.826.ca...@guybrush... Hi, every now and then while writing classes I forget to add the "function" keyword between my visibility modifier and the method name in a class declaration. I don't think it