Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes for Lua 5.2/5.3 compliance? #64

Closed
bmatsuo opened this issue Mar 8, 2016 · 4 comments
Closed

Changes for Lua 5.2/5.3 compliance? #64

bmatsuo opened this issue Mar 8, 2016 · 4 comments
Labels

Comments

@bmatsuo
Copy link

bmatsuo commented Mar 8, 2016

Do you have any plan to make the changes necessary to be a compliant environment for newer (minor) versions of Lua? Of course Lua 5.3.2 being the latest version as of today. I don't really have a need for it. But I think it would be nice.

One thing I have noticed as a difference between the lua C programs is that the lua5.3 interactive interpreter (REPL) works much better than the lua5.1 repl. Surely more work has gone into it's presentation but, having implemented a simple REPL in 5.1 and seen the limitations, I wasn't sure if it was actually just easier to build a good REPL using the 5.3 C API.

From what I understand the Go API has some functions that correspond to functions added to the C API in Lua 5.2. But I'm not entirely sure about C API changes in Lua 5.3.

Is the existing Lua module API strictly compliant exactly with Lua 5.1? Or is in somewhere in-between versions?

@yuin
Copy link
Owner

yuin commented Mar 8, 2016

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.

@bmatsuo
Copy link
Author

bmatsuo commented Mar 8, 2016

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?

@yuin
Copy link
Owner

yuin commented Mar 8, 2016

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.

@bmatsuo
Copy link
Author

bmatsuo commented Mar 8, 2016

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

Thanks for the great package :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants