21 replies to this topic

[WingedPanther73]

My personal philosophy: don't use goto EVER. I saw the link that talked about "rewriting to remove gotos". I admit it's tricky to remove them, but they were all examples where it wasn't needed in the first place. Boundary checking!

[marwex89]

I haven't used goto in a higher level language more than a few times, there are usually better ways to do stuff..

[debtboy]

i write code for my own purposes in c and i use goto.

For once I kind of agree...

We should follow best practices, and I can't think of a good reason to use it,
but that doesn't mean there isn't one and best practices is only a guide.
GOTO is a straight forward command that does what it says, no strings attached
GOTO exists in many languages... WHY?
(A good extension to this thread would be: Name all programming languages where goto exists)

I don't use GOTO, but if I had to work on someone else's code who does,
I wouldn't have a problem with it.

Additional NOTE:
GOTO exists in perl and I always heard there is
no wrong way to write a perl program.

[relapse]

No one uses Goto anymore because it sucks ** and is a plague upon decent coders. You get a bunch of n00bs jumping from line 560 to line 200, wtf? Ever heard of a function?

Goto == spaghetti code == **

[Donovan]

Interesting replies, I will be sure to keep a lot of this in mind.

[Alexander]

Do you get an award for digging up 7+ threads that are years old in one hour?

[Donovan]

Nope, but these are my old threads and I decided to check all my old threads just for ****s and grins and for memories..

[DarkLordCthulhu]

Gotos break the structural organization of a program. Most programming languages organize code into blocks. These blocks are discrete sections of code that execute under a certain condition or a certain number of times. If a goto is in there, then there is no longer any structure, the blocks are no longer discrete, and spaghetti code results. The main disadvantage of gotos is that they make code nearly impossible to read.