[Slice]

Quote:

Originally Posted by Vince Every self-respecting programmer will tell you that goto must never be used. It inevitably leads to spaghetti code and there are always better ways to solve it. To avoid "repeating the code over and over again", as you so nicely put it, functions were invented.

There are cases where it actually is a bit useful, but it's rare. In his example, he could just have refactored the if statements.

One place where goto is useful is obviously when dealing with #emit, but another place could be if you want to make a C-like switch statement with fall-through.

I've used it in strlib without feeling too bad about it, as well as here.

That said, always try to do what you do without using goto! It can cause undefined behavior and confusion..

For example, have a look at my goto usage in strlib here. I use "goto return_false" before the variable "ret" is instantiated - madness?!?!
goto modifies the FRM and stack. If you don't know what all these things mean, don't use it!