Changes for Lua 5.2/5.3 compliance? about gopher-lua HOT 4 CLOSED

I do not have any plans yet.
I did not see the Lua 5.3 codes, but I don't think Lua C API anything to do with the matter.

It is more important to make good use of rich console ui library like readline, prompt_toolkit, curses etc than Lua C API for improving the REPL environment. For example you can use chzyer/readline for that.

from gopher-lua.

You may be correct about the lua5.3 repl. I was just wondering if maybe parser error codes had changed in a way that made error handling easier to work out. That is not too important to me though.

I suppose I am just more concerned about staying current rather than falling too far behind. And, also wondering how I can help out. I have been enjoying use of gopher-lua so far, and am heavily exploiting it for my latest project.

Would you rather work towards more a complete implementation of lua5.1?

from gopher-lua.

On error handling, GopherLua has more structured API than C-Lua5.1 . #46 might be helpful for you.

Would you rather work towards more a complete implementation of lua5.1?

Lua 5.1 is considered as close to a “completed form”, and most widely used "specification" still in 2016(LuaJIT is upwards-compatible with Lua 5.1).

I have already implemented most of the Lua5.1 APIs, so I do not take an active interest in it.

from gopher-lua.

Ok. I understand. Thanks. Honestly I don't know what "most lua programmers" do most of the time.

Thanks for the great package :)

from gopher-lua.