Re: Writing interpreter in Lua

[Gopalakrishnan Subramani <gopalakrishnan.subramani@...>]

Does it mean, Lua JIT is not backward & forward compatible within minor versions?

I thought, the versions adds more libraries than core changes to JIT structure. I could be wrong. 

any way, If I distribute the lua dll along with solution, still the modification required in JIT structure? What I am assuming is that not get into Lua inside much, since my lack of language design, I could be wrong in my questions itself.

Thanks for answer.

--

Gopalakrishnan

On Fri, Nov 11, 2011 at 6:02 PM, steve donovan <steve.j.donovan@gmail.com> wrote:

On Fri, Nov 11, 2011 at 2:22 PM, Gopalakrishnan Subramani
<gopalakrishnan.subramani@gmail.com> wrote:
> 1. Should I convert the language to Lua byte code convention before
> execution?

Good question. This is the hard way to do it, although you get direct
control over the debug information.  But it will be tied to a
particular Lua implementation - e.g. if targeting Lua 5.1, it will not
work with Lua 5.2 without modification and LuaJIT has a completely
different byte code structure.

It is easier to know what's going on if you (at least initially)
generate Lua source.

The other option is to modify the Lua compiler until it gives the
syntax that you want. People have made curly bracket languages this
way ;)

steve d.