Re: RFC: Making T_FUNCTION optional in method declarations

On Sun, Nov 28, 2010 at 10:52 AM, Martin Jansen <martin@divbyzero.net>wrote: > On 28.11.10 16:14, Gustavo Lopes wrote: > > On Sun, 28 Nov 2010 14:58:13 -0000, David Otton > > <phpmail@jawbone.freeserve.co.uk> wrote: > >> 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. > > > > 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. > > At least one would have to use the following expression: > > (public|protected|private|final|static|function) functionName > > Just to be clear, this works on the assumption that we don't know the class name that the function resides in? I understand the search argument, but to me it only applies to functions, not methods. Is anyone arguing for removing the T_FUNCTION requirement on functions? > - Martin, -1 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >