gfvalvo:
Perhaps not, but if you had followed the suggestion in the sentence immediately following that statement: "Google 'structured programming'", you would have been provided with links to a plethora of information.
Did you read and understand my post? I clearly statned I was not looking for a plethora of information on the topic. I clearly stated I was looking for a simple and concise explination.
While I appreciate your answer it would be helpful if you would read the question to see if your response is really answering the question. Or if you are answer a question which was not bing asked.
I thought this was a friendly place were people are nice and help each other. No need to threaten me. I was just trying to get a question answered and be helpful.
I once made a robotic workcell with a MOTOMAN 6 axis robot. The programming language was a version of BASIC. It had the ability to call other programs from one program, with no structure, basically GOTO or spaghetti code. I had some jumpers in each fixture that identified the workpiece one from another, so the operator need only plug and play each fixture. From the "Main" program, I called smaller programs, which contained only the toolpath which differed from piece to piece. On the night shift, an idiot technician booted up the workcell after it was down for at least one shift. He had never read my technical manual on the machine. He decided to load the file named for the part to be run, which was only the toolpath, none of the sensor checks or other safety factors. As a result, he crashed the tool into the fixture, which was out of position. For spaghetti structure, I had to copy whole sections of the main program into each part file.
Doug101:
I thought this was a friendly place were people are nice and help each other. No need to threaten me. I was just trying to get a question answered and be helpful.
You wanted a concise explanation of why goto is frowned upon. I gave you one.
No-one threatened anything.
TolpuddleSartre:
You wanted a concise explanation of why goto is frowned upon. I gave you one.
No-one threatened anything.
Bad thinks will happen is what people say to others as a forum on intimidation and using right before they hurt or kill someone.
Why would you say "Bad things would happen" if that's not what you mean? You are not answering my question or providing any expliation of what you mean. I have no idea what you mean by "bad things will happen". The bad things I have hears about are school shootings and simiar killings.
Perhaps after making such a bold terse statement you coupld exapnd upon your though.
I took, "bad things will happen" as a threat and have reported your reply as a threat.
This thread has descended into paranoid silliness.
@OP, goto has been rightly deprecated and derided since the ascendance of structured programming.
In all but the most trivial cases of exiting multiple nested loop structures, it should never be considered.
goto is like replacing a fuse with a four inch nail, or taping down a safety switch because you want to drink from a can of Coke whilst operating a guillotine/press/.
It circumvents recognised safe programming concepts.