Code: (Select All)
IF Left$(user$,5) = "Steve" Then
...do stuff
GOTO end_check
END IF
IF Left$(user$,4) = "Jack" Then
...do stuff
GOTO end_check
END IF
IF Left$(user$,2) = "Jo" Then
...do stuff
GOTO end_check
END IF
...57 more unique cases to check and deal with...
end_check:Instead of GOTO, I use a 'Faux Loop' for similar situations.
Code: (Select All)
DO ' Faux Loop.
IF Left$(user$,5) = "Steve" Then
...do stuff
GOSUB end_check
EXIT DO
END IF
IF Left$(user$,4) = "Jack" Then
...do stuff
GOSUB end_check
EXIT DO
END IF
IF Left$(user$,2) = "Jo" Then
...do stuff
GOSUB end_check
EXIT DO
END IF
...57 more unique cases to check and deal with...
LOOP
END
end_check:
PRINT "We're done here."
RETURN So 60 extra 'EXIT DO' statements, but copy/paste makes that a snap.
This is more about style than optimization but I would have to ask myself, hmm 60 times, screw it, I'll use GOTO once in the code. I mean imagine if that WASN'T an option. That would suck. This it what I love about BASIC, little regulation and lots of options.
My dislike of using GOTO comes from my early Texas Instrument programming days when we needed to assign line numbers to every line of code. Change the line numbers when editing the code and it often blew up all the GOTO references, which then meticulously needed to be changed, as well. I'd also have to say GOTO statements were the #1 cause of spaghetti coding.
The few times I have used GOTO is in some very long routine where I want to circle back to something that just couldn't be done in a nested or recursive subroutine or if making my DO:LOOP nest meant many exits for parts of the routine that had nothing to do with what was coming down the pike. These types of situations put the spaghetti on the other foot!
-------------------
Like OldMoses, and I do like OldMoses, I also always use RESTORE and a label with all of my database calls. That really helps prevent database errors.
-------------------
JRace has a good point with combining math functions. I like the way doing that frees up space so I can see the next thing my code is doing, rather than jut all the calculations I know it needs to do. I just, again, wish we had a COLOR LABELS option in the IDE. That would be way cool! Right now I'm doing a colon search... oh wait, that doesn't sound good... to find my labels.
Pete
Shoot first and shoot people who ask questions, later.