When is Count1, 2, or 3 ever going to be other than event # ???
@SMcNeill this is why your example doesn't quite work: Take a rain event where it's -10 degrees and the wind is blowing at 120. In this case, the correct case is "Hurricane". However, your code will fall through without incrementing any of the counters.
Here, it's a simple one directional downflow of code, with expressive labels to indicate what's going on in the code. I don't really consider this "spaghetti code" as it doesn't weave up and down and get in a tangled mess, and I'd honestly have no issues at all in using GOTO in such a manner in my code. GOTO is a tool in our toolbox for a reason, and sometimes, it just makes sense. ;)
Hi @tomxp411,
please read the wiki page for Select Case and note well we have a EVERYCASE keyword here in qb64, which was actually used in @SMcNeill 's example.
But on the other hand I do also agree with you, that IFs without ELSE branch do it best here, what is actually what SELECT EVERYCASE does.
Yeah, GOTO is usually okay if you're branching forward and not out of control blocks.
For example, you should never do this:Code: QB64: [Select]
DIM WordList(1000000) AS STRING
FOR I = 1 TO 1000000
IF WordList(I) = UserWord$ GOTO Word_Found
NEXT
Word_Found:
IF I < 1000001 THEN
PRINT "Your word was found at position #"; I
ELSE
PRINT "Word not found."
END IFCode: [Select]DIM WordList(1000000) AS STRING
FOR I = 1 TO 1000000
IF WordList(I) = UserWord$ GOTO Word_Found
NEXT
Word_Found:
IF I < 1000001 THEN
PRINT "Your word was found at position #"; I
ELSE
PRINT "Word not found."
END IF
I can't think of a much simpler way to do the above than this, and it's easy to understand what's going on with it.
Code: QB64: [Select]
ON GOTO/ON GOSUB is one of my favorite tools in the MS BASIC toolbox, and it can be a good alternative to SELECT CASE for line-number BASIC when your domain is limited to a small, contiguous range of integer values. (Menus, for example, are a perfect place to use this.)
Honestly, I don't see anything wrong with what you've got here. (Though I imagine that GOTO would probably be in an IF condition or such instead of just stand-alone.)
It causes memory leaks, specifically in the stack.
FOR isn't a command which puts anything on the stack. Basically, a FOR... NEXT loop translates into something like the following:
FOR I = 1 TO 10
PRINT I
NEXT
Translates to: (a simplified version here, for illustration)
I = 1
I_Start:
PRINT I
I =I + 1
IF I <= 10 THEN GOTO I_Start
At the core level, a FOR loop is nothing but a self-contained GOTO loop. Using GOTO to exit it won't harm your program at all, nor affect any stack space.
Stack space mainly comes into effect when dealing with subs/functions and gosubs.