SELECT CASE, or something

[qbiscool]

or if you realy want to you could use goto's

input "hit a key"; j$
if j$ = "w" then
print "you hit w"
else if j$ = "r" then print "you hit r"
else print "you hit "j$
end if

or

on error goto goterror
print "hit a key or esc to exit"
do
key$ = inkey$
do
loop until key$ <> ""
print key$
if key$ <> chr$(27) then loop else system
system

goterror:
print "found error"
do
print "[r]etry, gnore, [f]ail"
do
key$ = inkey$
if key$ = "r" then resume
if key$ = "i" then resume next
if key$ = "f" then system
loop until key$ <> ""
loop

[TheBigBasicQ]

/me thinks aga is insane =P

Qbiscool. goto statements are dangerous at the hands of a newbie =(. So I would rather advice him to use gosub.

[Neo]

Qbiscool. goto statements are dangerous at the hands of a newbie =(. So I would rather advice him to use gosub.

So... you discriminate people on their knowledge and then say either 'YOU SHOULD USE SUBs' (experienced) or 'YOU SHOULD USE GOSUB' (newb)...

Ah, yes, I like Aga's example. It reads so much better. Some people may not like multiple statements on one line, but they sure make the code look nice. You can see the whole thing with one glance.

I'd really like it though if it had some identing...

[TheBigBasicQ]

No, i wasnt discriminating =P. I was just saying that goto is dangerous. I dont like GOSUB(personally) so I suggested SUB =).

[Neo]

*Inproper* use of GOSUB: Out of stack space
GOTO: Spaghetti code (sometimes causing stack error as well)
SUBS: Optimal procedural programming.

I think I agree with you

Btw, why, why, why does ON ERROR only support GOTO and not CALL SUB or so...

[TheBigBasicQ]

How how how should I know =P? But I dont find it inconvinient =P.

[Agamemnus]

Simple. My program modified to have tabs:

Code:

DO                                                      '7 tabs
INPUT "Enter the !#$!@#$@#$ key already!!", ikey        '1 tab
SELECT CASE ikey                                        '5 tabs
CASE "1": key1: EXIT DO                                 '5 tabs
CASE "2": key2: EXIT DO                                 '5 tabs
CASE ......
CASE ELSE: PRINT "INVALID!"                             '4 tabs
END SELECT                                              '6 tabs
LOOP                                                    '7 tabs

[TheBigBasicQ]

Simple. My program modified to have tabs:

Code:

DO                                                      '7 tabs
INPUT "Enter the !#$!@#$@#$ key already!!", ikey        '1 tab
SELECT CASE ikey                                        '5 tabs
CASE "1": key1: EXIT DO                                 '5 tabs
CASE "2": key2: EXIT DO                                 '5 tabs
CASE ......
CASE ELSE: PRINT "INVALID!"                             '4 tabs
END SELECT                                              '6 tabs
LOOP                                                    '7 tabs

I dont get the relevance?

[Neo]

Simple. My program modified to have tabs:

Hrmmm... where are the tabs?

I meant something like this:

Code:

DO
   INPUT "Enter the !#$!@#$@#$ key already!!", ikey
   SELECT CASE ikey
      CASE "1":
         key1: EXIT DO
      CASE "2":
         key2: EXIT DO
      CASE ......
      CASE ELSE:
         PRINT "INVALID!"
   END SELECT
LOOP

[Moneo]

Neo, I have a feeling that Aga doesn't waste time indenting or formating sample code. I guesss he figures if you like it you'll adopt it and format it to your taste.
*****l

[Agamemnus]

tBBQ: in response to Neo.
In regards to GOSUBs, I think that they're usually not necessary, but they still have use. I think that there could have been a lot more done with QB4.5's GOSUB/SUB thing, such as multiple layers:

1) Commands in one SUB don't respond to labels in other SUBs, but the label namespace is global not local. (ie. only one "blah:" per program)

2) GOSUBs are a nice organizational tool when you have a lot of SUBs or very few SUBs. Could make the IDE a lot cooler if you could see GOSUBs in a SUB, and maybe SUBs in SuperSUBs. (ie modules)

Neo: After the code and before the comments.

Moneo: Yup, yup, very sensible...

[qbiscool]

hey for that ON ERROR GOTO goterror could i use two ON ERROR's
like this:

ON ERROR GOTO 1
bload "",d,3

on error goto 2
open "" for output as #1
close #1

1
resume next

2
system

[whitetiger0990]

Like this?

Code:

CLS
ON ERROR GOTO 1
OPEN "aBaBaB1" FOR INPUT AS #1
ON ERROR GOTO 2
OPEN "aBaBaB2" FOR INPUT AS #1
CLOSE #1
END
1
PRINT 1
RESUME NEXT

2
PRINT 2
RESUME NEXT

hmm, guess so. it prints 1 and 2.
(and if you remove one of the OPENs it only prints one number so...)

[Blitz]

QBs error handling is the crappiest evarrr.

[TheBigBasicQ]

Nope you put only one ON ERROR statement. In order to check which error actually caused your error handler to be called you would use ERR command. Like this:

Code:

CLS
ON ERROR GOTO errhandler

CHDIR "e:"

END
errhandler:
IF ERR = 71 THEN
   PRINT "ErrorHandler: device not ready"
ELSEIF ERR = 76 THEN
   PRINT "ErrorHandler: Invalid drive specification"
END IF

RESUME NEXT

Change the drive letter to a non existing one and you will trap the second error while change it to "a:" and dont put any floppy into it and you will have it catch the first error =)