title: PHP and the goto statement to be added in PHP 5.3
body: <p>The "goto" statement comes straight out of ASM or any other assembler language.</p>
  
  <p>Here's a link: <a href="http://be2.php.net/manual/en/control-structures.goto.php" rel="nofollow noreferrer">http://be2.php.net/manual/en/control-structures.goto.php</a></p>
  
  <p>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.</p>
  
  <p>Can someone give me an example of a good use of this?</p>
  
  <p>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.</p>
  
  <p>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?</p>
  
  <p>Also: <a href="https://stackoverflow.com/questions/46586/goto-still-considered-harmful">A discussion here on StackOverflow about "goto" in general</a></p>
  
  <p>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.<br /> He told me a couple of times he did a good amount of programming in his days and mostly in FORTRAN and COBOL. Nowadays he does IT services,  server&amp;networkmanagment and such.</p>
  
  <p>Anyways, he said some stuff about "back in my day..."<br />
  After discussing that a bit, he came back to the goto statement, saying that even back in his days as a student, they allready knew it wasn't a smart idea to use it, but they didn't have much better back then. Try/catch was still years away and error handling hardly excisted.<br />
  So what did you do to check your program? Add a few lines at the end that allow you to print output and everything you need to check in your code, and then you place the line: "goto printing;", or something like that, to start the printing of your data.</p>
  
  <p>And in this manner, you gradually debugged your code.</p>
  
  <p>He agrees that the use of goto in the modern programming world is pretty useless. The only use he finds justified is an "emergency break", to be used in extreme debugging and unexpected situations. Kinda like <code>goto fatal_error;</code>, and have the "fatal_error" part of your code do some things to show you in-depth results.<br />But only during the creation of something. A finished product should not have goto-statements.</p>
  
  <p>LATE EDIT: <a href="https://stackoverflow.com/questions/19388/goto-command-in-php6">Another discussion about "goto" in PHP5.3/PHP6</a></p>