lua-users home
lua-l archive

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


Hi,

I followed the discussion on string.dump unavailability, and can live
with it for general code.

However, for a specific need I wrote in Lua a bytecode verifier to
characterize some subset of 'safe' bytecodes similar to what is
described in the Gems book.

I didn't succeed in my naive attempt to use jit.off(true,true) as the
first thing in the verifier module to make string.dump available locally
- so is this generally impossible, or is there some trick I don't know?

Somewhat related, is the non-JIT interpreter that ships with luajit 2.0
byte-code-compatible with the official Lua interpreter?


Thanks a lot in advance, Markus