Since this is a topic on Coding Efficiency, I want to take a moment to point out how foolish it is to listen to anything Pete might say on such a subject. After all, as he's illustrated countless times before, he STILL uses Inkey$ in his programs.
Hahahahahahahaha!! (Don't worry. If any else of you do, I'm not laughing at you. I just laugh at Pete.
)
Let me take a moment to explain:
INKEY$ and _KEYHIT are the *exact*, 100% identical, no kidding, gosh darn same command -- with one *minute* difference: one returns a string value, the other returns the ASCII numeric value of that string.
Inkey$ says "A", _KEYHIT says 65.
Inkey$ says CHR$(0) + CHR$(79), _KEYHIT says 19200. <-- this is the exact same value if yo MKI$ or _CVI the values.
Keyhit simply returns the numeric value of Inkey$. That's the only difference in the two commands.
BUT, it's inherently faster for several reasons:
1) Numbers are always faster than strings. Strings come with overhead numbers just don't have.
2) When it comes to extended keypresses, there's a LOT less to process than with Inkey$.
IF User_Input = 19200 THEN.....
IF User_Input$ = CHR$(0) + CHR$(79) THEN....
Compare the two IF statements above. Take just a moment to analyze them in your head. Which is OBVIOUSLY more efficient?
IF number = number.... <--- single comparison of 2 numbers. This isn't going to take long
IF string = CHR$ function conversion of number to string, added to, CHR$ function conversion of number to string...
Umm... I'm smart like Pete! Me thinks the second method is better! Me likes bananas and pew pew pistols and me brain is smaller than me hat!
Pete's example code:
And Steve's exact same code:
No UCASE$ needed -- the AND NOT 32 takes care of that. No ASC conversion needed. No string overhead. Just nice efficient code.
Unlike Pete's.
Hahahahahahahaha!! (Don't worry. If any else of you do, I'm not laughing at you. I just laugh at Pete.
)Let me take a moment to explain:
INKEY$ and _KEYHIT are the *exact*, 100% identical, no kidding, gosh darn same command -- with one *minute* difference: one returns a string value, the other returns the ASCII numeric value of that string.
Inkey$ says "A", _KEYHIT says 65.
Inkey$ says CHR$(0) + CHR$(79), _KEYHIT says 19200. <-- this is the exact same value if yo MKI$ or _CVI the values.
Keyhit simply returns the numeric value of Inkey$. That's the only difference in the two commands.
BUT, it's inherently faster for several reasons:
1) Numbers are always faster than strings. Strings come with overhead numbers just don't have.
2) When it comes to extended keypresses, there's a LOT less to process than with Inkey$.
IF User_Input = 19200 THEN.....
IF User_Input$ = CHR$(0) + CHR$(79) THEN....
Compare the two IF statements above. Take just a moment to analyze them in your head. Which is OBVIOUSLY more efficient?
IF number = number.... <--- single comparison of 2 numbers. This isn't going to take long
IF string = CHR$ function conversion of number to string, added to, CHR$ function conversion of number to string...
Umm... I'm smart like Pete! Me thinks the second method is better! Me likes bananas and pew pew pistols and me brain is smaller than me hat!
Pete's example code:
Code: (Select All)
Do
_Limit 30
b$ = InKey$
Select Case UCase$(b$)
Case "A" To "Z"
Print LTrim$(Str$(Asc(UCase$(b$)) - 64))
End Select
Loop Until b$ = Chr$(27)And Steve's exact same code:
Code: (Select All)
Do
_Limit 30
b = _KeyHit
Select Case b And Not 32
Case 27: System
Case 65 To 90: Print _Trim$(Str$((b And Not 32) - 64))
End Select
Loop
No UCASE$ needed -- the AND NOT 32 takes care of that. No ASC conversion needed. No string overhead. Just nice efficient code.
Unlike Pete's.