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
Hi,
I was pulling my hair out trying to get a script to work and finally found in the documentation that string.pack isn't implemented.
While it would be nice to see string.pack/unpack implemented, I would like to suggest that standard functions which are not complete raise a different error than "Can not call a nil value". I would say just implement a stub function that raises a different error like "Not implemented. See documentation."?
Cheers,
Russ
The text was updated successfully, but these errors were encountered:
It will be helpful for others that may stumble on it. I'm not concerned about the implementation, if I need string.pack, there is now NLua available in 5.3.5. NeoLua is more suited to my current use case exposing .Net classes, rather than being a Lua engine.
NLua uses the lua.dll, so it is full compatible with c-lua by design (language/runtime).
NeoLua is a implementation of the lua-langauge with .net extensions and has a basic implementation of the lua-runtime (it translates the calls to .net functions).
I implemented all functions, that I need for scripts, that our company uses. Other people helped me on other functions... But overall this part needs more attention.
The next big part on my roadmap for this project, will be a redesign of the runtime. But I am busy with other projects, currently.
Hi,
I was pulling my hair out trying to get a script to work and finally found in the documentation that string.pack isn't implemented.
While it would be nice to see string.pack/unpack implemented, I would like to suggest that standard functions which are not complete raise a different error than "Can not call a nil value". I would say just implement a stub function that raises a different error like "Not implemented. See documentation."?
Cheers,
Russ
The text was updated successfully, but these errors were encountered: