If this ever happens, it's bad design in the first place. If you solution is applied, you code is guaranteed to break after the first two or three changes.Suppose this happens, you will most definitely need to use a goto.
For nested loops: In C you might be right. In C++ you can use exception handling. After all, something interrupting your nested loops should be highly exceptional. Or it should exit the function at this time. I don't see a need with proper function design to place a goto statement.
I have never used a goto statement in C/C++. Last time I used it was Atari Basic when I was too inexperienced to know what a loop is. ( And VB, but there it's really just another method of exception handling ).
Actually, using goto is not that bad. It's just that from my experience, people using it made mistakes in their concepts and tried to remedy them this way. And goto should not be used to make dirty code clean up a hopeless concept.
We are always talking about how a goto might be useful. Can anyone here give a real life example ? Can anyone give me a portion of code that isn't solvable by proper planning alone ?
No assumptions, not guesses, a real world example ?
Edited to add:
Right, the use of goto would violate our coding standards and my code would be considered wrong no matter how fast it runs.At my current employer, use of the goto statement would violate the installation standards and hence fail the quality departments tests.