[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Backport of Lua 5.2 "in" scoping (was Re: Lua registry, environment, and threads.)
- From: Luiz Henrique de Figueiredo <lhf@...>
- Date: Fri, 8 Jan 2010 14:29:59 -0200
> I'm interested whether the patch is correct. From the other thread I
> thought I understood that functions would stop using the environment
> they were defined in by default, and instead the environment they are
> called in. Such that this simple example would fail (due to lack of
> print in env):
>
> function sayhello() print("Hello") end
> env = { sayhello = sayhello }
> in env do sayhello() end
>
> Am I wrong in my understanding? If so then the change really has less
> consequences than I first thought.
% lua
Lua 5.2.0 Copyright (C) 1994-2008 Lua.org, PUC-Rio
>
> function sayhello() print("Hello") end
> env = { sayhello = sayhello }
> in env do sayhello() end
Hello
- References:
- 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., Enrico Colombini
- Re: Lua registry, environment, and threads., Roberto Ierusalimschy
- Backport of Lua 5.2 "in" scoping (was Re: Lua registry, environment, and threads.), Mike Pall
- Re: Backport of Lua 5.2 "in" scoping (was Re: Lua registry, environment, and threads.), Matthew Wild