[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Let's not break existing scripts.
- From: <AllanPfalzgraf@...>
- Date: Thu, 10 Nov 2011 16:52:17 -0500
"Just never upgrade"
That would be fine if your work never required the capabilities in some
I will reluctantly go ahead with a conversion to whatever 5.2 requires
just to not be cut off from the community. Hopefully, the things that
break will be clearly broken - not 'kind of working' such that
reasonable but incorrect results are produced.
Lua appears to have a history of making breaks with the past when it
made sense. What may be different this time is the volume of work done
with 5.1 that likely is greater than that done with previous versions.
Considering the work needed to bring all the shared and private work
forward, it is less painful than bloating Lua with the capability of
supporting two (and more later with the precedent set) versions or doing
the same to all the existing scripts.
Date: Thu, 10 Nov 2011 14:12:33 -0200
From: Luiz Henrique de Figueiredo <firstname.lastname@example.org>
Subject: Re: Let's not break existing scripts.
To: Lua mailing list <email@example.com>
Content-Type: text/plain; charset=us-ascii
> I would like to put this very clearly: I am very much against the
> prospect of Lua 5.2 breaking ANY script written for 5.1.
> It's just a pain and it changes the impression of Lua being something
> that "just works" to something that "breaks when you upgrade it".
> Python has not been the same since the 2/3 rift was introduced. I
> really really really want Lua to avoid this. 5.1 has a huge basis
> which is very important to keep sane and working IMO.
You seem to misunderstand the dynamics of Lua. You never just upgrade
Lua, you consider if the new Lua is good for your needs and then adapt
Lua is not like Firefox...
You can keep whatever version of Lua is suitable for your needs
Just freeze the source code into your project.
Many people have done just that...
lua-l mailing list
End of lua-l Digest, Vol 16, Issue 47