LOL don't say "GOTO" is going to be taken away from a BASIC dialect, to a certain book author who insisted on the keyword because he didn't like "DO... LOOP" for silly reasons. He was compelled to use "WHILE... WEND". The book was about "systems" programming with M$QuickBASIC v4.0.
If "GOTO" is taken away from BASIC it would have to be taken away from C as well. All of it, including the functionality C didn't have in the 1980's involving pointers, which opens possibilities for self-modifying code. (Oh no I already said it, am I going to be banned?)
If "GOTO" is taken away from BASIC it would have to be taken away from C as well. All of it, including the functionality C didn't have in the 1980's involving pointers, which opens possibilities for self-modifying code. (Oh no I already said it, am I going to be banned?)
(10-24-2022, 06:03 PM)Dimster Wrote: I realize this is off topic Pete but, if we are heading towards the elimination of GOTO, wouldn't it be nice if we could just code ON ERROR resnxt (or whatever the label is carrying the coding handling the error. Maybe if its a label then perhaps it should read ON ERROR :resnxt. A topic for another thread.Take away the colon then "resnxt" should be a subprogram. Not a "FUNCTION".