Menu
▾
▴
#797 Lua lexer update for Lua 5.2
LexLua update in anticipation of Lua 5.2 beta. Lua 5.2 is currently in alpha; although highlighting-related changes elicited little discussion, it's just possible that things might still change. To be patched at a time you deem suitable.
Lua 5.2 highlighting changes:
(a) hexadecimal floating-point numbers recognized
(b) support for '\*' whitespace escaping in strings
LexLua and test cases
This ticket and the patch was posted by me, for the tracker record. I was logged in a couple of hours ago -- can't seem to rely on the connection recently.
In what sense can't you rely on the connection lately? You should know (it was on the list) that the email announcements of postings to this tracker are now moderated due to the rash of spam we had earlier in the year.
Posts will not get through until either Neil or I approve the post.
If that was not clear to you from traffic on the mailing list, let us know, maybe we should make another announcement.
(Aside: The spam traffic has fallen off considerably, I don't know if the spammers gave up or if google (or sourceforge) started doing something to block most of the spam. We might consider eliminating moderation again on a trial basis, but I won't recommend this before discussing it with Neil. (This might be the prompt to Neil to see what he thinks.)
Yes, I'm aware of the moderation. Nothing to worry about, I made some recent postings on the bugtracker without realizing that somehow the page had logged me off. Never had a problem with this before.
This might be related to a local connectivity problem if logon state is tied to IP address (old copper lines), or the earthquake messed some cables around the Pacific Rim, or I wasn't aware of some kind of new SF logon timeout. So I've switched to the 2 week cookie now, that might work better for me.
These changes appear OK for old code and they can be updated if anything is removed from Lua 5.2. Committed.
There have been a few messages lost due to the extra hop in moderation. Some proportion of mail messages always goes missing particularly from bulk senders like SourceForge bug updates and groups moderation.
There was a Feature Request that I didn't see any mails about (including any moderation message) and I only noticed a week later when looking at the feature list. This just means I'll have to check the tracker pages occasionally.
If there are no spams for another 2 months then maybe turn moderation off. I expect that the spammers are using a smarter retry algorithm that accounts for people getting tired of moderation. It was certainly noticeable at one time that if a single item got through there'd be a pile but if it failed retries would be slowed down to something like one a day.