browse keys (@bk)

[Kenneth Brody]

"Jay R. Ashworth" wrote:
[...]
> True, but that does not necessarily imply -- the fact that filePro
> doesn't care which case you press the key in -- that the *system dummy*
> will return it's reply in a specific case.
> 
> Happens it will; I just tested it: even if you press "X", what you get
> back in @BK is "x".

@BK will contain the keystroke you pressed, and will retain the case that
you typed.

If I press a lower-case letter, @BK contains that lower-case letter.  If
I press a capital letter, @BK contains the capital letter.

>  I don't know whether I think that's a feature or a
> bug; I do know it's not documented.  *Anywhere* -- it should be in
> 18.11.2.11 of Stuart's fourth, but it's not.

Well, it is implied, by saying that it contains the key you used.

> But more importantly, how come "=" is acceptable on an IF line?

Because you can't have assignments on an if line, so "=" is available to
unambiguously mean "check for equality".

> I see that that is in Stuart's book, but ISTR that it used to give
> syntax errors; when did it start working?

Version 1.0, over 20 years ago.

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+