On Sat, Jun 16, 2012 at 12:53:57PM -0400, Gedalya wrote: > Well, I'm using 5.1, never upgraded to 5.2. I'm a little confused, > if I'm using 5.1 and writing legitimate 5.1 code, then the case is > that my code was broken by installing a new version of this > extension - and presumably I did nothing wrong?
I mean, the same luasql sourcecode works for 5.1 _and_ 5.2 > The lua code is my own, not a debian package, is that what you meant to ask? OK, so I'm not breaking an existing Debian package. > I'm gonna try once again with luasql = require 'luasql.mysql' and > see if it indeed works, but the question remains, did I write "good" > code that just broke for no reason. Actually assigning to a local variable the result of require is a good Lua practice. What was wrong was the behaviour of require that was assigning a global variable, a sort of unavoidable side effect that was escaping any form of sandboxing. Lua 5.2 fixed that. But you are right, the upgrate broke legitimate code, so this is a bug. How to deal with it is a bit unclear to me. If Tomas thinks luasql should be fixed, I'll try to upload an updated version of the package before the freeze (that will be really soon!). If the change was intended, I'll just add a note in NEWS.Debian. Cheers -- Enrico Tassi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
