On Sun, 2005-11-27 at 15:54, Zeev Suraski wrote: > > We *can* screw it if we go in the wrong > direction, and adding redundant features which > are useful in rare cases and much more likely to > be abused than to be properly used is a good step > in that direction. A lot of people are saying we > already went too far with PHP 5, and that's > arguable. It's clear, however, that adding more > and more language features and making PHP more > and more complex is not a good recipe.
While I agree that PHP is not Perl, nor would I want it to be, the goto construct would improve the clarity of code and would be more useful to less experienced developers than attempting to retool the while or do/while constructs into emulating the same functionality. Additionally the goto construct is an order of magnitude faster (and I'd argue clearer) than setting a state variable and checking it's value via switch cases or if/elseif/elseif/.../else. I mean the argument constantly being made against goto is that newbies will shoot themselves in the foot, well from what I've seen newbies very often shoot themselves in the foot regardless of the measures taken to prevent such an outcome. Seriously, if a newbie can understand polymorphism, then can we not give them the benefit of the doubt that they can understand goto? Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
