The Word GOTO is not as bad as the word Hardcoded
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
It's like "OH MY GOD! THE NUCLEAR REACTOR'S GONE CRITICAL!!!" Um, yeah. That's when it produces the electricity.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
Off Topic my favourite goto label was hell, saw it in a code review //error handle goto HELL; still makes me chuckle!
-
Off Topic my favourite goto label was hell, saw it in a code review //error handle goto HELL; still makes me chuckle!
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic. Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot. To this day, all tech writers must earn my respect before I trust what they write.
-
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic. Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot. To this day, all tech writers must earn my respect before I trust what they write.
R_L_H wrote:
Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot.
If GOTO is bad, why do all processors have them (jumps)? I always snarled whenever some idiot would proclaim that if it were in their power they would eliminate assembly language.
R_L_H wrote:
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic.
I agree, I learned to program before structured code and GOTOs were necessary and I certainly spent time digging through code that loop-de-looped because either the programmer thought they were clever, didn't want to restructure the code, or were incompentent to begin with. See this[^], actual production code from a commercial database program from the 80's. Needless to say, we trashed that code as soon as we found it. The original programmer thought he was genius as evidenced by the thousands he was making a month in royalties.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic. Still, one tech writer writes an article calling a simple op-code "evil" and 30 years (or thereabouts) later we still think anyone using a GOTO command is a programming idiot. To this day, all tech writers must earn my respect before I trust what they write.
R_L_H wrote:
GOTO was never the problem-- prevalent abuse of the keyword and poor code structure was the epidemic
No tech writer ever told me it was evil. Nor did common knowledge. I know from personal, painful, first-hand experience. Things got a lot more manageable when function calls were invented, but by then GOTO had its bad reputation. And back before function calls, it wasn't abuse -- it was the only way to write a program.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Seriously, The end users just love to say well just hardcode it to always work that way. At least with GOTO they don't know it exists. With Hardcoding they have heard it and the users like it because it sounds like a sledge hammer to them and they love to sledge hammer things into submission.
To err is human to really mess up you need a computer
