On 06/16/2012 12:45 PM, Enrico Tassi wrote:
On Sat, Jun 16, 2012 at 11:52:53AM -0400, Gedalya wrote:
My report is poor in detail, I'd be happy to provide more if someone
tells me how :-)
No, it is perfect. The point is that the statement
require 'foo'
sets a global 'foo' table in Lua 5.1, but in Lua 5.2 it does not
and the idiom is indeed
foo = require 'foo'
this release of luasql works for both lua 5.1 and 5.2, so I think the
author tried to provide a consistent semantics (he is in CC, in case I'm
wrong, please speak up).
Now, the fix is rather easy on your side:
luasql = require 'luasql.mysql'
What I'm missing is if the software that broke is in Debian or not.
In case it is, I should reassign the bug I guess.
In case it is not I can add a NEWS.Debian to alert users upgrading.
Cheers
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?
The lua code is my own, not a debian package, is that what you meant to ask?
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.
require 'luasql.mysql'
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
