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

Make Lua optional #233

Open
Tracked by #240
naturallymitchell opened this issue Jan 25, 2019 · 4 comments
Open
Tracked by #240

Make Lua optional #233

naturallymitchell opened this issue Jan 25, 2019 · 4 comments

Comments

@naturallymitchell
Copy link
Member

With conditional compilation of Lua we could open the door to other scripting languages.

@Arnaz87
Copy link
Contributor

Arnaz87 commented Jan 26, 2019

We'd have to make some module in charge of exposing bindings to the languages, and choose, either at runtime or at compilation, which language to use. We'd have then to use only the minimal common features to both languages, which means we have to drop object orientation, iterators, varargs, and other advanced features of lua in the bindings (I think I particularly was the one making the most use of them in the bindings I wrote) and keep only basic functions with basic data types.

@naturallymitchell
Copy link
Member Author

rename most variables lua.anything to env.anything or, at worst, torchbear-env.anything

@naturallymitchell
Copy link
Member Author

Arnaud mentioned that Lua is class + method based, which he reflected in the bindings to match that, but that it is also possible to do it in a generic, functional way. This would support both function setup layouts, when cfg.feature Lua or another language is used.

@naturallymitchell
Copy link
Member Author

We can completely replace the Lua C-based interpreter with Rust-based Mun.

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

No branches or pull requests

2 participants