[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Could Lua itself become UTF8-aware?
- From: "Soni L." <fakedme@...>
- Date: Mon, 1 May 2017 10:15:38 -0300
On 2017-05-01 10:00 AM, Roberto Ierusalimschy wrote:
What is wrong with
Again, missing character in font.
function functiοn ()
There was a long discussion about that a few years ago:
There is no missing character in font nor keywords being used as
identifiers. Both | | ("en quad", a kind of white space) and
|functiοn| (with a omicron for "ο") would be valid identifiers with
the proposal (accept everything above 127 as valid in identifiers).
I want to be very clear that I am not against Unicode, quite the
opposite. However, "accept everything above 127 as valid in identifiers"
is quite different from supporting Unicode (again, it is quite the
opposite). For data, the Lua approach is that it gives a very basic
support and leave the rest for specialized libraries. Several programs
have been using Lua with Unicode quite successful (e.g., Lightroom and
However, the Lua lexer should not depend on libraries. It would be great
if the lexer could handle Unicode (correctly!), but I don't know how to
do it without at least doubling the size of Lua. To do it (very) broken,
I prefer to keep it as it is.
But my latin-1! (why limit it to UTF-8 if you can just add support for
pretty much every single extension of ASCII instead?)
Disclaimer: these emails may be made public at any given time, with or without reason. If you don't agree with this, DO NOT REPLY.