Is it OK to exit a "switch" statement with "Return"?

[mbunds]

Back in my early days programming GWbasic, I caused stack-overflow errors by exiting for-next loops ungracefully with "goto" commands.

In those days, there was no "exitfor", no "Do-While/Until", no "Select-Case"; if I remember correctly, when we wanted to exit a loop prematurely, we had to "goto" a routine that would "pop" unused iterations off of the stack.

I have an example script that "returns" out of a case statement, and am wondering if this is acceptable form?

(Snippet from Henry Aymans "Phone Book Rev 02")

While 1
        $nMsg = GUIGetMsg()
        Switch $nMsg
            Case $GUI_EVENT_CLOSE
                Shtdown()
                Return
            Case $cmdNext
                cmdNext_Click()
            Case $cmdPrev...

 

[water]

I see no harm to exit a function like this.

[mbunds]

8 minutes ago, water said:

I see no harm to exit a function like this.

Thank you kindly! 

I wanted to be sure because I didn't learn about my error in GWbasic until the program had been running for a considerable amount of time.

[MilesAhead]

18 hours ago, mbunds said:

Thank you kindly! 

I wanted to be sure because I didn't learn about my error in GWbasic until the program had been running for a considerable amount of time.

I didn't learn about my error programming using GWBasic for a long time!!  heh heh

Just kidding.  I also did QuickBasic 3.0 for a while.  Now if I try to use FreeBasic I struggle with the syntax.  It has so many compatibility modes that just about every function call syntax I try looks right but generates a syntax error.