K-user mailing list

[Radu Mereuta <headness13 AT gmail.com>]

Unicode is not properly supported by the parser that we use so you can only refer to ASCII characters in a K definition.

Radu

K Developer

On Wed, Dec 12, 2012 at 3:38 AM, Joshua Cranmer <cranmer2 AT illinois.edu> wrote:

Hi, I'm back again with another question.

I'm trying to make sure that my semantics work properly given non-ASCII characters, so I made sure to have my parser emit all non-printable characters in Strings using the \uXXXX escape sequence, but it appears that Strings don't support this escape sequence, nor do they support the \xXX variant. Is there any way to properly input non-ASCII characters in strings?

On a similar note, what do lengthString/charString/asciiString assume about the size of characters? What would charString return for an integer in the range [128, 255)? [256, 65535)? [0x10000, 0x17FFFF] (i.e., non-BMP characters)?

Also, is there an easy way to hook into upperCase/lowerCase semantics as defined in the full Unicode character set? I don't really want to have to write yet another translation script to copy the unicode case folding tables...

--
Joshua Cranmer
Source code archæologist

_______________________________________________
k-user mailing list
k-user AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/k-user