They will have to rip my right to use a goto LABEL statement from my cold dead hands! :-) I prefer a goto when needing to break out of deeply nested loops, although more experienced programmers recommend nesting while loops instead of a goto. However, I think the goto is very intuitive and easy to understand in a flow chart situation, and should be used for clarity.

I guess the real issue is way down in the C-compiler and ultimately the underlying assembly language. Which is more efficient in number of computer operations, energy usage, etc. Nesting complicated loops, or using a simple GOTO LABEL.

I watched a youtube video of an assemby expert, who dissected compiled C-code programs, and rewrote them more efficiently in assembly, discarding alot of c-code library bloatware. He could change a 20k sized c-utility to one in pure assembly of only 2k, and it ran way faster. I would leave to smarter programmers than I, to devise a test which timed the goto usage, vs. nested loops method. See Reusable threads demo for the origin of this challenge of mine. :-)