Something doesn't quite seem right to me about a position that has both of the following assertions: 1) goto should not be available 2) there's already an equivalent of goto available, so goto is not needed (and it's just fine that people use the equivalent)
If you really believe "1", shouldn't you be arguing for some sort of a warning if someone uses "2"? If you really believe it's OK for people to use the equivalent, wouldn't you rather have people use a method of expression that more clearly states their intentions? I heard a story of someone who was extremely proud of a language he/she had written because it only had "for" and not "while" (or vice versa). The argument was that it was so much clearer to have a single construct and anything that can be done with one can be done with the other. Do the people supporting position "2" regret having both "for" and "while"? I think most programmers appreciate the ability to express themselves with the full vocabulary of standard constructs (even if some of them don't get used very often). Whether "goto" gets added or not, I hope it is for a consistent set of reasons. - Todd -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
