Re: Backport of Lua 5.2 "in" scoping (was Re: Lua registry, environment, and threads.)
[
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: Mike Pall <mikelu-1001@...>
- Date: Fri, 8 Jan 2010 19:17:41 +0100
Roberto Ierusalimschy wrote:
> (The indices of the upvalues for the new closure also
> are now stored in struct Proto, so that OP_CLOSURE does not need those
> OP_MOVE/OP_GETUPVAL pseudo-instructions after it.)
Yes, I did that in LuaJIT 2.x, too. I've also put the prototypes
objects themselves into the constants table to avoid managing an
extra growable table. And the constants table is type-specialized
(GC objects below pt->k, numbers above pt->k) to reduce memory
usage.
--Mike
- References:
- 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
- Re: 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.), Roberto Ierusalimschy