adambiser: Yes, because they've added constructs to the language in order to work around the fact that they don't have GOTO. Java added loop labels as a way to break out of outer loops from an inner loop (about the only "valid" reason for a goto). I don't think C# or C++ do, but then they have goto which you must either use or restructure your code in ways that might not be as easy-to-read.

That said, GOTO should be completely avoided.

hedwards: Well, yeah, I mean part of the reason I hate GOTO statements with such a passion is the way that they were implemented in BASIC. If you needed to add code somewhere in the middle of the program you had to worry about having every GOTO that referenced a line after that was fixed. I assume that there were IDEs that dealt with that, but I didn't have access to them.

hedwards: Hmm, that's an interesting question, I wonder how many were used in the FreeBSD kernel. I guess I'll have to whip up a quick script to count them. Although given the number of files that could take a bit.

wodmarach: yeah auto line renumbering existed in many IDE's (they even changed the goto's to the correct numbers)

wodmarach: Yeah basicly the lower level your coding the more GOTO's have a reason and a use.

hedwards: Well yeah, I know when you start working on assembly you end up having to do that sort of thing all the time as I don't believe that there are other options. Or at least in the few times I've looked at assembly I haven't seen folks with a different method.

wodmarach: JMP is one of the most used commands in assembler JMP is a goto

wodmarach: at last count the Linux kernal had over 90k goto's do not generalise. GOTO it's very handy in baremetal coding.