Provide means for Orbiter to pass which Lua version it is using · Issue #568 · orbitersim/orbiter · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Orbiter could somehow communicate through the Lua Interpreter which version of Lua it uses, that would permit add on developers the opportunity to maintain backward compatibility with different Lua (and related Orbiter) versions for deprecated methods.
For example, Lua 5.1 uses a loadstring function to convert a string of text into an executable statement. After 5.1 that is deprecated and absorbed into the functionality of the load function.
The text was updated successfully, but these errors were encountered:
That seems that it would work. Searching for _VERSION, I find LUA_VERSION and several other useful globals like LUA_RELEASE in Lua.h. Is the usage in the script _VERSION, or LUA_VERSION, or am I looking at the wrong globals?
This would be a handy bit of information if it could be found in the documentation somewhere. It's not in Orbiter_lua.chm.
Seeing that there are few other Lua global variables, it might be useful to document just this in the Orbiter_Lua.chm, and pointing the reader to www.lua.org for further information.
If Orbiter could somehow communicate through the Lua Interpreter which version of Lua it uses, that would permit add on developers the opportunity to maintain backward compatibility with different Lua (and related Orbiter) versions for deprecated methods.
For example, Lua 5.1 uses a loadstring function to convert a string of text into an executable statement. After 5.1 that is deprecated and absorbed into the functionality of the load function.
The text was updated successfully, but these errors were encountered: