[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: Mon, 11 Jan 2010 15:33:43 +0200
On Mon, Jan 11, 2010 at 3:26 PM, Fabio Mascarenhas <mascarenhas@acm.org> wrote:
> in orbit.htmlify() do
>
> function my_view()
> return html{ body{ p "foo" } }
> end
>
> end
That's actually an expressive syntax, but not having access to module
scope within these functions _would_ be irritating.
Current thinking is that getfenv/setfenv is available, just not quite
so conveniently. Use the debug functions, or if that is considered
horrible, load the fenv module dynamically. As long as lua_getfenv
exists, all will be fine ;)
steve d.
- References:
- Lua registry, environment, and threads., Christian Tellefsen
- 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., Alexander Gladysh
- Re: Lua registry, environment, and threads., Cosmin Apreutesei
- Re: Lua registry, environment, and threads., Matthew Wild
- Re: Lua registry, environment, and threads., Cosmin Apreutesei
- Re: Lua registry, environment, and threads., steve donovan
- Re: Lua registry, environment, and threads., Fabio Mascarenhas