Is there a reason people don't use goto's?

"goto's are considered better practice" By whom? The reason there are iterative constructs like while, for, and do are so they can simplify what will eventually become a bunch of jump statements when compiled. I'm not sure which language you're using, but there's already a idiom for this: for (;;) { /* Body */ } If you use a goto statement then you're unable to use break and continue within the body. Consider the following: for (;;) {   /* do something */   if (something)     break;   /* do something else */ } If you were to remove the for statement entirely and rely on goto, you'd have something like this: loop: /* do something */ if (something)   goto out; /* do something else */ goto loop; out: Are you saying that the second option is easier to read and understand? What rubbish. It makes your code needlessly bulky, and a good compiler will generate similar code for both situations. Goto statements can be useful if a function may return at many parts due to errors (for example), and it has to perform a common task before returning. Instead of rewriting that same task over and over again, you can write it once with a label before it and jump there from the multiple points. Aside from that situation, I haven't found many parts where it makes more sense to use a goto statement. I've heard people suggest that nested loops are a good situation where using a goto statement may be necessary, but it's usually better to break your code up into two functions in that particular case.

Just took a look at codes I've written over the years, the only "goto" used are in assembly programs. I'm mostly a C programmer.

A Goto jump is inefficient and inelegant and is rarely used in serious programming or questions.

Some people with poor code writing ability have produced program hard to maintain by having bad structures replete with goto's that overlap each other's block. The result is that some languages are trying to make do without goto's, and that some claim that goto's are the mark of poor programming skills. Which is the equivalent of saying that cars are bad because some people drive while being drunk. Goto's are efficient, that is the only real jump command in the resulting assembly and machine language once a program is compiled, if it is good enough for a CPU, why not for a programmer? I have seen my share of poor programs, some of which were not using any goto's.

In the programming language I've learned go to's are not considered good practice. Maybe the language you're learning/using is different, but you're not stating which one you're using.

I never used goto in my life lol. I program in C++ and Java. I either use loops or if in a function when its easier recursion.

This has got to be a troll post.