|Pavel R. 7adbc171f6||3 months ago|
|.devcontainer||9 months ago|
|.github/workflows||7 months ago|
|build-utils||7 months ago|
|docker/linux-ubuntu||7 months ago|
|include||3 months ago|
|mir||3 months ago|
|patches||3 months ago|
|ravicomp||3 months ago|
|readthedocs||7 months ago|
|src||3 months ago|
|tests||5 months ago|
|vscode-debugger||7 months ago|
|.clang-format||2 years ago|
|.gitignore||1 year ago|
|.gitmodules||3 years ago|
|.travis.yml||7 months ago|
|CMakeLists.txt||7 months ago|
|LICENSE||2 years ago|
|Makefile||1 year ago|
|README.md||3 months ago|
|lua-config.cmake.in||2 years ago|
|ravi-config.h.in||7 months ago|
|ravi-env.bat.in||2 years ago|
|ravi-env.linux.sh.in||2 years ago|
|ravi-env.osx.sh.in||2 years ago|
Ravi is a dialect of Lua with limited optional static typing and features MIR powered JIT compilers. The name Ravi comes from the Sanskrit word for the Sun. Interestingly a precursor to Lua was Sol which had support for static types; Sol means the Sun in Portugese.
Lua is perfect as a small embeddable dynamic language so why a derivative? Ravi extends Lua with static typing for improved performance when JIT compilation is enabled. However, the static typing is optional and therefore Lua programs are also valid Ravi programs.
My motivation is somewhat different - I want to enhance the VM to support more efficient operations when types are known. Type information can be exploited by JIT compilation technology to improve performance. At the same time, I want to keep the language safe and therefore usable by non-expert programmers.
Of course there is the fantastic LuaJIT implementation. Ravi has a different goal compared to LuaJIT. Ravi prioritizes ease of maintenance and support, language safety, and compatibility with Lua 5.3, over maximum performance. For more detailed comparison please refer to the documentation links below.
deferstatement for releasing resources
Lua 5.4 relationship to Ravi is as follows:
<const>variables - not planned.
<close>variables - Ravi has
'defer'statement which is the better option in my opinion, hence no plans to support
Ravi should be able to run all Lua 5.3 programs in interpreted mode, but following should be noted:
Limit name Lua value Ravi value
MAXUPVAL 255 125 LUAI_MAXCCALLS 200 125 MAXREGS 255 125 MAXVARS 200 125 MAXARGLINE 250 120
When JIT compilation is enabled there are following additional constraints: