The "goto" statement comes straight out of ASM or any other
assembler language. Here's a link:
http://be2.php.net/manual/en/control-structures.goto.php I'm
wondering: what can this do to make my code more well-organized?
How can I implement this in larger projects, without screwing it
up. Since the goto will allow you to jump back and forth,
accidental assignments and infinite loops are waiting to happen
if you use this the wrong way. Can someone give me an example of
a good use of this? EDIT: allright, I've seen some of the
replies and apparently a wide consensus exists about the use of
the "goto" statement and it being bad. So I'm still wondering:
why would PHP bother to add it to the language. If they didn't
see something in it, they wouldn't do it... so why? EDIT2:
Seeing as this question induced a lot of bad things to be sad
about the goto statement, I went and asked my father. He's 52
years old and is an Industrial Engineer. He told me a couple of
times he did a good amount of programming in his days an