[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Hooks, tailcalls and tracing LuaJIT
- From: Benoit Germain <bnt.germain@...>
- Date: Fri, 8 Apr 2011 16:57:50 +0200
2011/4/8 Michal Kottman
<k0mpjut0r@gmail.com>
I don't think the code is entirely correct (it fails on multiple
variables of the same name in one scope), but I went for simplicity and
it works correctly for variables of the same name in different scopes.
Also, some tinkering had to be done with the level for locals, because
when accessed, the `level` parameter for a local is different than when
created.
That's what I implied: solving this particular problem is non-trivial, and the service offered is sufficiently useful that proposing an official implementation deserves some consideration.
--
Benoit.
- References:
- Hooks, tailcalls and tracing LuaJIT, Geoff Leyland
- Re: Hooks, tailcalls and tracing LuaJIT, Mike Pall
- Re: Hooks, tailcalls and tracing LuaJIT, Luiz Henrique de Figueiredo
- Re: Hooks, tailcalls and tracing LuaJIT, Benoit Germain
- Re: Hooks, tailcalls and tracing LuaJIT, Michal Kottman