[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Lua registry, environment, and threads.
- From: Roberto Ierusalimschy <roberto@...>
- Date: Fri, 8 Jan 2010 11:31:02 -0200
> > It will still change the environment of its caller, but for
> > compatibility only. This will be a documented compatibility behavior,
> > because it affects new code. (Outside the "in module() do ... end" you
> > will still be inside the module...)
>
> I guess someone will be surprised by this then:
>
> in module("foo") do
> ...
> end
> print() -- Fails rather unexpectedly.
That it was I meant by "it affects new code".
-- Roberto
- References:
- Re: Lua registry, environment, and threads., Patrick Donnelly
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Christian Tellefsen
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Mark Hamburg
- Re: Lua registry, environment, and threads., Patrick Donnelly
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Mike Pall
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Re: Lua registry, environment, and threads., Mike Pall