[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Lua registry, environment, and threads.
- From: steve donovan <steve.j.donovan@...>
- Date: Thu, 7 Jan 2010 19:33:27 +0200
On Thu, Jan 7, 2010 at 6:52 PM, Mark Hamburg <mark@grubmah.com> wrote:
> More on the forthcoming "in env do ... end" construct...
It is already half-way towards a 'using' statement, i.e. something
that could guarantee finalization of the given object.
> 2. The above mucks with being able to lint the code since we are actually fine with the global reads of addField and the global set of baz.
True, but static analysis is already hit-and-miss in Lua.
The trouble (as with Pascal with) happens when such such constructs
are nested. Would this statement nest as expected, i.e.
in e1 do in e2 do
-- will fallback to lookup in e2, then e1
end end
steve d,
- References:
- Lua registry, environment, and threads., Christian Tellefsen
- 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., Mark Hamburg
- Re: Lua registry, environment, and threads., Mark Hamburg