9 replies to this topic

[tesla1889]

title asks it all

EDIT: i only ask to know if i should plan for compatibility

[Cloudy]

Doubt it. Would break a lot of programs.

[Kingdaro]

getfenv() and setfenv() were both removed in 5.2. For good reason, I hope.

[tesla1889]

Kingdaro, on 09 February 2013 - 07:05 AM, said:

getfenv() and setfenv() were both removed in 5.2. For good reason, I hope.

there are work arounds for both of those involving the added _ENV table. i ask because i often find myself using those and i want compatibility

[NeverCast]

ipairs was also removed in 5.2, Though there are alternatives. This would break many programs also.

[Kingdaro]

ipairs isn't removed, it's only deprecated.

tesla1889, on 09 February 2013 - 12:40 PM, said:

there are work arounds for both of those involving the added _ENV table. i ask because i often find myself using those and i want compatibility

I tried screwing around with _ENV, but could never fully figure it out. I'll look up a tutorial or something later on.

[tesla1889]

_ENV is the environment table

a workaround for setfenv would be

setfenv = function(fn,env)
if (type(fn) ~= "function") or (type(env) ~= "table") then
error("invalid args")
end
env.main = fn
env.oldenv = _ENV
return function(...)
_ENV = env
local t = {main(...)}
_ENV = oldenv
return unpack(env.t)
end
end

[hvenev]

I need lua 5.2 for my scripts.

There is an implementation of {get,set}fenv for lua 5.2. https://github.com/d.../lua-compat-env

[Cranium]

It's not happening. Stop bringing it up.

[Lyqyd]

Also, I have no idea where the ipairs being removed/deprecated nonsense came from, since Lua 5.2 adds an __ipairs metamethod.