It is important to note that the statement Djikstra made regarding GOTOs was in the late 1960s-a result of studying numerous programs where the use of GOTOs, combined with the relative lack of programming structures, made the code hard to follow, error-prone, and difficult and costly to maintain.

The statement that GOTOs are bad is now taken almost as dogma, but what must be kept in mind is this: if the use of it improves whatever metric you choose to look at, be it read/maintainability in code that must be maintained in production for a lengthy period of time or efficiency in an application where performance is a major issue, then by all means the use of it should be allowed.

Remember that another solution may also exist, though, and may be preferrable, especially if style or style conflicts are an issue, others who must assist in maintaining code have difficulties from their use, or if their use starts to become abusive.