Pete's Dumb Idea of the Day!

[TempodiBasic]

Well with Select Case you would use...

Code: (Select All)

 

Rem  demo Restore : On x Restore idea    vs Select Case

For x = 1 To 4

     Select Case x

        Case 1

            Restore data1

        Case 2

            Restore data2

        Case 3

            Restore data3

        Case 4

            Restore data4

    End Select

    Print "----------------------------------------------" 

    Read number, nam$, Order$

    Print number, nam$, Order$

Next

End

data1:

Data 1,one,the first

data2:

Data 2,two,the second

data3:

Data 3,three,the third

data4:

Data 4,four,the forth

Pete

Yes Pete you're right
please pay attention to the fact that the FOR loop starts with a value 0 that hasn't been managed by Select case and it triggers a runtime error, while in the complex and tortuose way of ON x GOSUB ... RESTORE /RETURN  it goes on.
In other words, 0 has been used to simulate an unpredictable value of X. Using Select case you must sure that X takes always a predictable value. Using the tortuose way you can avoid this task of predictable value.

All the good and clever ways posted here need to know how many data field are in the code and must sure that it would be used the range of that value in the code.
Please pay attention: 
the tortuose way is not better than the others, but it is nearer old fashion way of coding when DATA was a new great opportunity to bring informations into code.
And in my mind DATA is a good resource of the past.

It's fun and useful getting infos and experiences of professional coders.