Lua Update

[xoft]

@worktycho ToLua is already handling global arrays bad (the g_BlockLightValue exported manually in DeprecatedBindings.cpp doesn't work), so we might have to start maintaining it at least a bit.

[worktycho]

We already have a custom fork. The question is whether we should stay with our fork, or switching over to something like SWIG, to just writing something from scratch (tolua's code is horrible, single letter variable names all over the place).

[NiLSPACE]

Isn't this what we're looking for if we'd want to go to Lua 5.3? Their wiki isn't complete yet, but looking at the feature list I think it supports all we want.

[sphinxc0re]

Didn't we discuss the implementation of LuaJIT? What about that?

[SamJBarney]

For building the bindings, if we had to build our own generator, I suggest using LibClang.

---

Perhaps with an updated version of this binding: https://github.com/mkottman/luaclang-parser

[NiLSPACE]

@sphinxc0re We tried LuaJit in a hackish way, but the speed improvements weren't that great: https://forum.cuberite.org/showthread.ph...4#pid19494

[DiamondToaster]

I made a plugin a while back that actually somewhat strained the regular Lua implementation and saw noticeable speed improvements while using LuaJIT. The benefits are MUCH more noticeable when running on a really low-spec system (ARM board).

[worktycho]

The use of libclang would need a significant change to our build system significantly, because we wouldn't be able to build it as part of our build without causing serious problems. (significant build time increases for clean builds, source files generated by programs built from generated sources...). I've no idea about the use of doxygen.