unchar() seems to be broken

[sshilovsky]

kos 0.20.1. log follows.

PRINT UNCHAR("A").
Failed to set scalar value.  Passed type Char, expected Double or Int
__________________________________________
           VERBOSE DESCRIPTION
Failed to set scalar value.  Passed type Char, expected Double or Int_________
_________________________________
__________________________________________
At interpreter history, line 24
PRINT UNCHAR("A").
             ^

[dewiniaid]

I thought I opened an issue for this myself but apparently not. I can confirm I've experienced the same issue.

This also means there is currently no means of case-sensitive string comparisons save for maybe some hackery involving a case-sensitive Lexicon. (Add both strings to new case-sensitive Lexicon, then check its length)

[Dunbaratu]

I confirmed that this is still happening in our latest develop build.

I'm guessing this will be a simple one-line fix. Let me look at it.

[Dunbaratu]

Root cause of problem found:

ScalarValue.Create(foo) expects foo to be some kind of number type like int, float, double, etc.
But char is also an integer type - just a very short one, and ScalarValue.Create() doesn't have a case for that type.

I'd like to see ScalarValue.Create() cover more of the number types in the future, but for the time being I'll just cast the (char) to an (int) in Unchar() before calling it - just so we can get a fix to you quickly.