Since a few of you have poked me about this thread now...
First, internals@ is the place where we make decisions like this. We don't poll the "community" or any such sillyness. We use our collective experience to make a decision.
I personally can easily live without GOTO, but I really don't see the great harm in adding it. Yes, it can be misused, but at same time we have traditionally not shied away from features that have the potential for misuse. The biggest driver architecturally from day one has been code transparency. I don't see GOTO as being vague or obtuse in any way. It isn't a magic operator that nobody understands or confuses. It will do exactly what people expect it to do, and we can document it to death to try to aleviate misuse, but in the end our job isn't to force people to write pretty code that wins beauty contests. Our job is to provide an efficient solution to a problem and if people feel they can solve their problems in a clearer and more efficient way with GOTO then I don't think we should stop them from doing that.
-Rasmus
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
