We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be useful to support Lua programming language in CASR the same way as Python (casr-python) and Javascript (casr-js) programming languages.
casr-python
casr-js
On an unhandled error, Lua generates a traceback like below:
LuaJIT:
[0] ~/sources$ luajit -e "error('crash')" luajit: (command line):1: crash stack traceback: [C]: in function 'error' (command line):1: in main chunk [C]: at 0x63a219b032e0
Lua:
[0] ~/sources$ lua -e "error('crash')" lua: (command line):1: crash stack traceback: [C]: in function 'error' (command line):1: in main chunk [C]: in ? [0] ~/sources$
Manually traceback can be generated with debug.traceback("message") 1, error("message") 2, see 3.
debug.traceback("message")
error("message")
https://www.lua.org/manual/5.4/manual.html#pdf-debug.traceback ↩
https://www.lua.org/manual/5.4/manual.html#pdf-error ↩
https://www.lua.org/pil/8.5.html ↩
The text was updated successfully, but these errors were encountered:
hkctkuy
No branches or pull requests
It would be useful to support Lua programming language in CASR the same way as Python (
casr-python
) and Javascript (casr-js
) programming languages.On an unhandled error, Lua generates a traceback like below:
LuaJIT:
Lua:
Manually traceback can be generated with
debug.traceback("message")
1,error("message")
2, see 3.Footnotes
https://www.lua.org/manual/5.4/manual.html#pdf-debug.traceback ↩
https://www.lua.org/manual/5.4/manual.html#pdf-error ↩
https://www.lua.org/pil/8.5.html ↩
The text was updated successfully, but these errors were encountered: