You know, that article is WAY overused. Remember that it came from a time when people were using line-numbered gotos and creating contstructs (loops) from gotos. My personal (and somewhat informed) opinion is that sometimes a labeled goto can simplify a loop exit in such a manner that one line could replace
conditionals. In the case where a goto replaces multiple conditionals inside a loop, this not only makes the code more readable but it can also make the code run exponentially faster (conditionals take clock cycles). The article you referenced is about people abusing the goto and the need for more friendly/readable constructs that would help make more maintainable code. If the occasional goto helps move more to that end, then use it.