On Tue, 2013-02-19 at 17:08 -0700, Levi Morrison wrote: > Let's stop pretending that the vast majority of PHP users actually > grep source code looking for `function foo`.
That was never said, but there's a big number of people who has to deal with code produced by others and doing tasks where it is not always appropriate to startup and IDE and create a project and index it and "grep" is not always a simple grep but some more complex operation involving a search. And as you are happy with your idea you can certainly create shortcuts so you can type "puf" or such instead of "public function" and maybe even to hide the "function" word. > 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. The ones who don't know about 'grep' are happy about the extra clue. > 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. The argument for removing (or rather: the argument for adding yet another alternate syntax) is even weaker. Code is more often read than written. Now let's focus on work. johannes (who will now ignore this thread - we're turning in circles) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
