The story on goto 1

[MrMoocow]

Okay,
I'm doing a sorta "poll". Even though I'm "know my way around VB" I took a VB course in order to be able to take a C++ class. My instructor insist that goto's are improper in any case. On the subject of Error handling it says you shouldn't have errors. So I would like some replys saying wether or not you use goto.

Thanks. Brad,
Hey! email me any time! Bradsvb@yahoo.com

 

[chiph]

Peter -
Did you ever work with the Apple ][ disk drives? It used a 6-bit byte, called a "nybble".

Chip H.

 

[petermeachem]

No, I can't claim that one. I have worked on the Link GP4. That was very interesting. The programme were all read from a rotating drum so you couldn't loop, all progress was forwards. If you wanted to jump, you jumped to a specific label. If you forgot to put the label in, the computer would just skip all instructions until it found another instance of that label. This could be a considerable distance, you could easily skip over a complete engine (on flight simulators). It also had, I think, 4 parallel processors. You knew exactly how many machine cycles a multiply took, so you had to either put no-op's in until the multiply returned with the value, or you could do a few logic operations whilst waiting. This didn't help much with understanding the code. Completely unrelated things would be popped in to fill a gap.

Ah, the old days. Peter Meachem
peter@accuflight.com

 

[WilMead]

GOTO does not create spaghetti code, programmers do.


Wil Mead
wmead@optonline.net

 

[rkpdm]

Nothing wrong with using GOTO if used sparingly.