http://www.allegro.cc/forums/thread/589282

You don't need it, if you know how to use these instructions properly: do-while, switch, if-else.
Goto is ok for Basic programmers, but in C/C++ you have better and more elegant alternatives.
I have never used a goto in my C/C++ projects, and I will never do it.

Use goto when it makes your code clearer. It's often used where you would use catch and finally blocks in java, ie. for jumping to some error cleanup code at the end of a function. And sometimes it's the cleanest way of breaking out of nested loops. But if you're using it to jump backwards, you better make sure there really isn't a better way. I've seen some messy code doing backwards jumps.

BP's right; the break and continue keywords are actually controlled goto's.

I think historically goto got a bad rap from back in the fortran/cobol days when that was all they had; Fortran didn't have if/then/else for a LONG time. Cobols paragraph structure is a sort of controlled procedure branching construct that goto would desrupt. If you goto'd/jumped out of a paragraph, the pgm would execute straight thru to the end. Then in the early MS basics like that on the c-64 all you had was goto and gosub.

In the 60's some guys proved that any flowchart could be implemented using only if/then/else and a pre-test loop like while(){}. That's one thing that led to the 'structured programming' revolution. It's hard to believe that something we take for granted and seems so obvious was revolutionary at one time.

Goto is the way you handle exceptions in Visual Basic.

Goto is the buldozer of coding. Sometimes, the buldozer is just the right tool for the job. Not often, but sometimes.

"Why does a dog lick its penis?"
"Because it can."

I think goto is the most strange thing in C/C++. We all know it belongs to BASIC. We also know that it is a part of the standard C/C++. But I bet it is the only thing coders find strange, something that doesn't match the way of thinking and way of using the language.

I speak a kind of old Swedish (because I live in Finland), which is not influenced by English in same extent than the Swedish spoken in Sweden. It strikes me every time I see or hear a new English word in Swedish printed or spoken in Sweden, used as if it were a part of the language. But not only words. Some structures in sentences are also adapted from English. I find it horrible. A bit like using goto in C/C++.

Ok, you might be right, there are more oddities than goto. I never knew about trigraphs. I bet they go way back to the time when all computers used 7 bit ascii for everything. I have my Bondwell 16 in my attic (next to my Sinclair ZX81). It used 7 bit ascii and to be able to show scandinavian letters Å, Ä and Ö, it replaced [ \ ] with Ä Ö Å. On a very low system level. It was burnt into the 128k bios ROM.

I didn't code in C at that time, but I coded in Pascal. And instead of writing FooÄ16Å, I wrote Foo(. 16 .)

On a standard English/US machine that would be Foo[16]

if(Bad == true)
         goto Hell;

Hell:
   Death = true;
   Burn = true;
   Pain = true;

So we're all going to hell no matter what?

No, only if Bad == true

Oops, how could I miss that? I'll blame it on almost never using goto. Yes, that was it...

This is fixed in C++0x, by the way.