Yes I understand that, but it will make lua54.dll more fat. Maybe once users are using it and making reports about bugs. It's too soon to make it in the LuaRT core.
LuaRT 1.9.0 released
just an idea: freely selectable modules
a TUI or GUI to select your modules to be static linked in your luart.exe
[] c
[ ] math
[ ] debug
[ ] utf8
[*] string
[] table
[*] os
[ ] io
[*] coroutine
[ ] compression
[ ] sysutil
[ ] ui
...
Yes it's a good idea, making it available for wrtc
ruby I have started a similar program - see [Login to see the link]. I can save my programs and parameters in it and generate an exe file from it. This means I don't always have to enter the parameters again. It worked with LuaRT 1.8. Now I am about to test it on LuRT 1.9.
Samir The advantage of luajit is that the execution is very fast. Indeed, luajit sacrifices some flexibility for extreme speed (but the official lua vm also sacrifices a lot of flexibility for extreme compact size). Another advantage of luajit is that it has a complete and time-tested mature ffi, and all battery libraries of luajitrt can be written in pure lua via ffi.
Thank you for the feedback I will check this