when I want to migrate to the new Lua,
I faced the big problem is "table.getn" is no longer exist. so
I still use Lua 5.1.
mailing list <firstname.lastname@example.org>,
Fosdem talk on pain of moving from Python 2.x to 3.x
We've been using Lua 5.1 as a tool to give our users scripting
functionality for nearly 10 years now. It's working well, but as our motto
is not to break backwards compatibility, it seems at this point we are
eternally stuck with 5.1 as I'm not seeing much by the way of migration
tools being available. There are just custom patches to future Lua versions
that add backwards compatibility, but building a non-standard Lua version
is another whole world of pain.
Is anyone in a similar position? How are you looking at
migrating to newer Lua versions?
The talk goes into details of how challenging it was to move the
Python user base from 2.6 to 3.x. It seems that the process needed
active help and support from the Python team. It made me think of the
pain in the Lua community in migrating from 5.1 to 5.3. I recently
installed the new developer edition of Redhat Enterprise Server - of
course the stock Lua is 5.1 still.