> And my point still remains. There are an awful lot of PHP programmers out > there who really don't need an extra way to write for(), or while(), or > do..while(). It makes maintenance work harder when you have a mixture of > styles in there to cope with. > > I don't for a moment believe that Sara intended her GOTO implementation to > be used as a simple alternative construct in any old situation that comes > along, and that's where much of the point of this whole discussion lies. > Because you can bet your ass that many coders out there will do just that > thing.
My point was to say it's powerful, as powerful as all those, not that it could replace them.. I would still use while(), do..while() and for() the times they are intended for.. I'm sure most of the people would.. There are however situations where goto is what makes sense.. Even if it can be done with do..while() or try..catch(), goto is just the real logic way to do it.. Instead of not adding it, add warnings to the manual.. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
