[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: A rant about backward-incompatible changes
- From: Coda Highland <chighland@...>
- Date: Tue, 14 Jul 2015 08:09:44 -0700
On Tue, Jul 14, 2015 at 8:05 AM, Simon Cozens <simon@simon-cozens.org> wrote:
> On 15/07/2015 00:03, Daniel Silverstone wrote:
>> The one Lua-based project I have which really doesn't play nicely with multiple
>> lua versions simply refuses to work if the version is not the one it is written
>> for.
>
> I think the take-away here is that each minor revision of Lua should be
> regarded as a different language. If that's the policy, then, fine, I'll
> run with it.
>
As a different dialect of the language, at least, yes, akin to the
difference between Python 2 and Python 3. (LuaJIT is also a different
dialect of the language.) A good distro will install them as slotted
packages that can coexist.
As Lua's primary goal is to be embedded, applications that run from
the system-installed Lua interpreter are a fairly recent development.
For most deployments you're expected to roll your own Lua.
/s/ Adam
- References:
- A rant about backward-incompatible changes, Simon Cozens
- Re: A rant about backward-incompatible changes, Luiz Henrique de Figueiredo
- Re: A rant about backward-incompatible changes, Simon Cozens
- Re: A rant about backward-incompatible changes, Rob Kendrick
- Re: A rant about backward-incompatible changes, Simon Cozens
- Re: A rant about backward-incompatible changes, Coda Highland
- Re: A rant about backward-incompatible changes, Luiz Henrique de Figueiredo
- Re: A rant about backward-incompatible changes, Simon Cozens
- Re: A rant about backward-incompatible changes, Daniel Silverstone
- Re: A rant about backward-incompatible changes, Simon Cozens