Re: RFC: Making T_FUNCTION optional in method declarations

+1 if "While technically possible this RFC suggests that the following shall NOT be valid for keeping the code readable " also means that the patch implements it as well (force the function visibility property usage). 2010/11/27 Pierrick Charron <pierrick@webstart.fr>: > +1 > > 2010/11/27 Johannes Schlüter <johannes@schlueters.de> > >> 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 is required for readability and it is not >> needed by the parser to prevent conflicts, I therefore propose the >> following RFC incl. patch to allow writing >> >>        class Foo { >>            public bar() { >>                echo "Hello World"; >>            } >>        } >> >> 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/~johannes/php/zend_optional_t_function.diff >> >> johannes >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org