>> The key question for me is: does removing it hurt PHP in any way? And >> for me, the answer is a clear and resounding no. I do not grep code >> for method definitions: I know exactly where they are and so will my >> IDE if I happen to not be using vim. And for those who like to grep >> for method definitions they can keep the keyword present. > > Except when I come along and try to grok your code. I rarely search my > own code.
Protip: use an IDE. No, I'm serious. I work from the command-line a lot. I grep, awk and sed a lot of things on a weekly (sometimes daily) basis. However, it does not replace a good IDE. Ever done a replace from the command line only to find out you messed up some binary files and/or git/svn information? Happens all the time when I don't use an IDE; good IDE's don't make that mistake. Let's stop pretending that the vast majority of PHP users actually grep source code looking for `function foo`. They don't. *They don't even know how to use grep.* However, every PHP developer has to write `function` and more importantly they have to read `function` over and over again. --- Does that mean that I think `function` ABSOLUTELY SHOULD BE made optional? No. I don't. Am I tired of everyone complaining about this particular issue and pointing to the fact that some external tool won't work if you remove the otherwise unnecessary keyword? Yes, I am. Take a step back and look at your argument guys: you may have strong personal feelings about it, but it's a pretty thin argument. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
