I don't agree that Lua version are that much different. The API is pretty stable.

Funny, I've regularly updated Lua for my openFrameworks bindings, from 5.1 all the way to 5.4 over the years and have not had major issues. I think I am simply not using any real end case features to where it matters. So far SWIG is handling the bindings generation well enough and I do add whatever small shims are needed via macros, but so far that has only been on the C side. The Lua side has been stable for me.

On Oct 3, 2024, at 12:00 PM, pd-dev-request@lists.iem.at wrote:

On Wednesday, October 2, 2024 at 11:39:30 AM CDT, Christof Ressi <info@christofressi.com mailto:info@christofressi.com> wrote: On 02.10.2024 18:30, Timothy Schoen wrote:

...

Currently, pdlua is not compatible with luaJIT, since it was updated to Lua 5.4 (and uses some of the new features internally). It's possible to port it back to luaJIT by taking out all the new Lua bits.

Both have some advantages and disadvantages. But for me, regular Lua would win (but only by a small amount). The reason is: it's architecturally simpler, more mainstream, more widely used/tested, and (in my estimation) more likely to be maintained for a very long time. luaJIT is very fast, so I'm not opposed to it either. Having any kind of scripting for objects available at all is the most important thing here 🙂

If LuaJIT stopped working for whatever reason, we could still use vanilla Lua 5.1 - which will continue to work as long as we have C compilers :) Lua is a bit peculiar in that every minor version is really a different language. Once you pick a Lua version, you typically don't upgrade, unless there is some very compelling reason.

Personally, I'm using Lua 5.3 and I would also tend towards Lua 5.3 or 5.4. We just have to be aware that once we pick a version, we basically have to stick with it because of backwards compatibility.

Christof

-------- Dan Wilcox danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/