Re: Lua standard library - thread-unsafety

[William Ahern <william@...>]

On Thu, Jun 28, 2012 at 02:12:02PM +0900, Miles Bader wrote:
> William Ahern <william@25thandClement.com> writes:
> > It seems to me that people don't so much want to keep using Lua 5.1,
> > as they want to keep using LuaJIT. But those people have a real
> > dilemma on their hands, because Mike will never add _ENV
> 
> Link?  I've never seen him say that....
> 

From: http://www.freelists.org/post/luajit/LuaJIT-Roadmap-20122013

	But there's one important message: compatibility with Lua 5.1 is
	there to stay!

	Many users of LuaJIT, especially those with big code bases, have a
	heavy investment in Lua 5.1-compatible infrastructure, tools,
	frameworks and in-house knowledge. Understandably, they don't want
	to throw away their investment, but still keep up with the newest
	developments.

	As I've previously said, Lua 5.2 provides few tangible benefits.
	LuaJIT already includes the major new features, without breaking
	compatibility. Upgrading to be compatible with 5.2, just for the
	sake of a higher version number, is neither a priority nor a
	sensible move for most LuaJIT users.

	To protect the investment of my users and still provide them with
	new features, LuaJIT 2.1 will stay compatible with Lua 5.1.

From: http://permalink.gmane.org/gmane.comp.lang.lua.luajit/210

	Re: [ANN] LuaJIT Roadmap 2012/2013

	Xavier Wang wrote:
	> What about _ENV? has some plans to add it into luaJIT?

	That would need bigger changes to the VM. Also, this has an
	influence on the Lua/C API, which would break compatibility.

	_ENV isn't any better than getfenv/setfenv for the practical use
	cases. Also, all global accesses would get slower, so there's little
	reason to add it.

	--Mike