Quote:
Originally Posted by Trollheart
Like I said, not a clue. But why are goto's frowned upon?
|
Essentially, as programs progress in their lifetimes (and I've worked on code older than I am), the more go-to's you have (which are essentially unstructured jumps from one part of the program to another), the more difficult the program becomes to understand, the more difficult it becomes to maintain, and the more time and money needs to be spent to work with and modify them.
You might think you've got it figured out in a program with 15 different Go-To's, but then after promoting to production, you get your ass completely burned.