|No such thing as a small change|
Actually, I have used goto in production when there was a perfectly good construct, namely the continue block.
(What, you had to click and find out what it did? Hrmmm... maybe goto is more maintainable from a knowledge standpoint.)
I had a large while loop that iterated over an array that was constructed earlier. I did some stuff, then had a set of if-then statements. Yes, I could've built this out to be a series of functions, but, as this was the meat of the script, didn't feel that was warranted. I did want to be able to "return" out of the first if-block and continue processing after the last else. So, I put a label up, called it DONE, and used goto quite liberally.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
In reply to Re: Re (tilly) 2: Fear of Large Languages (was: "Would you use goto")