browse keys (@bk)

[Kenneth Brody]

"Jay R. Ashworth" wrote:
[...]
> > If I press 'a', @BK is "a".  If I press 'A', @BK is "A".
> 
> I tested it with something like
> 
> :@bk eq "x":show popup "little x";end:
> :@bk eq "X":show popup "BIG X";end:

ITYM:

:@bk eq "x":show popup "Either an upper- or lowercase 'x'";end:
:@bk eq "X":show popup "A major malfunction has occurred!";end:

> And I got little x both ways; we aren't trying to say that "eq" isn't
> case sensitive, are we?

Are you saying that eq _is_ case sensitive?  (It certainly looks that
way, since that's the only way your code could work.)

[...]
> > > Noted.  But that doesn't explain why I *can't* use the traditional
> > > companions thereto (>, <, etc), which is the real question.
> >
> > Because those still have the "normal" filePro meaning, even on an IF line.
> 
> Yeah.  I see it.  I'd have gone for consistency, I think, and outlawed
> "=" too, but maybe it's just me.

I think this one falls under the "don't use it if you don't want it"
category.

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