lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Sun, Nov 1, 2009 at 12:59 AM, Mike Pall <> wrote:
> An innovative trace compiler is integrated with advanced, SSA-based
> optimizations and a highly tuned code generation backend.

Seeing as LJ is already tracing all Lua calls that are executed, could
it not have an option to export this information in a form that would
facilitate code browsing? This is a common problem when familiarizing
oneself with a large code base.  From static analysis, it is
practically impossible to know what code paths are implied by the
simple call 'obj:method()'

The exact format is not important, only that it is parseable ;)

steve d.