> Goto is a plainly bad idea. Yes it has its uses, but 99% of > the time it would just be completely, mercilessly, utterly abused.
Its not good or bad, just a language construct. Its how you use it. > As the people taking the language forward, it's the > responsability of PHP developers not to introduce features > that you just know in advance are going to drag the > language's standards downhill. Magic_quotes and > register_globals have provided plenty of flak already -- > let's not introduce things that we KNOW will generate problems. "We are not giving you 'goto', because we can't trust you with it"? > > Uh? EVERY parser generater that I know of uses goto, and it's > > definitely not a problem if the generate 'spagetticode' - as nobody > > ever has to even look at that code. > > If you want to build a full-blown parser, PHP is not your > language. If you need a code generator, you have a problem. Why not? Applications like phpMyAdmin attempt to parse SQL. Why can't they use the right tool for the job? Jared -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
