Re: RFC: Making T_FUNCTION optional in method declarations
| From: | Gustavo Lopes | Date: | Sun, 28 Nov 2010 15:14:00 +0000 |
| Subject: | Re: RFC: Making T_FUNCTION optional in method declarations | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50659@lists.php.net to get a copy of this message | ||
On Sun, 28 Nov 2010 14:58:13 -0000, David Otton <phpmail@jawbone.freeserve.co.uk> wrote:
2010/11/27 Johannes Schlüter <johannes@schlueters.de>:IDEs would not be a problem, they would certainly be updated to locate definitions under the new syntax. As to grep, surely you could use another regular expression, perhaps egrep -rs "(public|function) functionName" or something similar. This seems like a false problem, it's not like it's hard to locate definitions in C or Java codebases... -- Gustavo LopesWithout T_FUNCTION token. In my opinion an access modifier /public, private protected, static, final) should still be required for keeping readability.As a plea on behalf of maintenance coders dealing with large, messy codebases, please, please don't impact our ability to run 'grep -rs "function functionName" *', or hit F8, or whatever your IDE's equivalent is.