I think goto is a good thing to have, although (outside of assembly language) it would mostly not be needed since other ways would work better. The example give

I think goto is a good thing to have, although (outside of assembly language) it would mostly not be needed since other ways would work better. The example given there probably should not need goto (since it is just a simple loop), although if it uses goto, that isn't much of a problem anyways. A break and continue statement is basically like a goto, and in some cases is more convenient since it automatically knows where the target is and you do not have to add a label there yourself. But, a return statement is not really the same as goto (although some instruction sets, such as MIX, implement it as such).