Yes I know that now , I still think goto's have a place somewere its a nice feature to have if you dont overuse them all over the place. I love you goto`s even if know one else does!
I agree that in small programs it can be useful but if you get used to using them and don't learn how to do things the proper way your code will be impossible to debug. Seriously, I have been sitting in front of the computer looking at my own code from when I first started programming and thinking "What was this idiot trying to do." then I realize "Hey that idiot was me".
TheHeadFL pretty much said everything I was going to say when I read the question - down to the example he posted about breaking out of multiple loops .. Perhaps, both of us have read the same books. lol
Traditionally, don't do it. It makes for poorly organized code which is difficult to read. There are always alternatives to using the "goto". The example mentioned, is one exception to the rule - where it is actually more "clearer" to use goto. But, keep in mind that "most of the time", the situation will not call for a goto statement and will be considered to be poor style.
I admit that could become a long if statement if you had 50 or 60 for statements which brings me two the secound way I would do it. I would just make the whole nested for a int function and in the if statment have it return 0 which would exit the function and the loop.
The goto I guess would work too but if any of my teachers ever saw a goto statment in one of my program that would be a automatic many point off.