Jonathan Sauer wrote:
Then I think string.uppercase and string.lowercase should point to the corresponding function in the unicode library to prevent confusion and bugs. Or is there a reason to keep the old functions around?
sure, because they are part of the official lua libraries and these are taken as is, of course you can redefine them yourself strings.lower = unicode.utf.lower etc
When tracing assignments, the ones made from Lua are flagged as being \global (BTW: What are these messages about `reassigning [no_local_whatsits]'?): That is a bug, actually. It is currently using a non-initialized stack variable for the global/local decision, and I could make it do either.
I do not quite understand which part of the above text you are adressing. Which one is a bug? The global assignments made from Lua, or the reassigning of [no_local_whatsits]? Inferring from Hans' mail, I would suspect the latter.
indeed Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------