IronLua is intended to be a full implementation of Lua targeting .NET. Allowing easy embedding into applications and friction-less integration with .NET are key goals.
It's built with C# on top of the Dynamic Language Runtime.
Licensing has not been decided upon yet but it will be some form of permissive free software license for easy contribution and usage without any fuss.
This is very much a work in progress project and isn't near a usable state yet.
-
2011-06-30
Started work on lexer. -
2011-07-05
Lexer has all major functionallity and can lex entire Lua. Still some bugs that will be fixed while working on parser.
Started work on parser. -
2011-07-17
Can parse entire Lua. Probably have lots of minor bugs that will be fixed when I pull in the test suites.
Have begun reading up on DLR. Will probably take some time reading documentation of the DLR before I start working on the runtime and translation of the AST to DLR expressions. -
2011-08-09
I have decided to rewrite the project in C#. It should be pretty straightforward to port. -
2011-08-15
Rewrite to C# is done. The rewrite was done for several reasons. The binary size is 4 times smaller, probably because of F#'s discriminated unions and closure's generated code among other things. Additionally tooling is alot better for C# and it is easier to reason about code performance because the IL generated is more easily mapped to C#. -
2011-09-14
IronLua can now generate expression trees for its entire AST. Currently working on function invokation, specifically mapping arguments to parameters. It's a quite a complex process involving type coercion and casting, expanding varargs, using parameter and type default values if not enough parameters and wrapping overflowing arguments into "params" and Varargs parameters.
After that I will start working on all the TODO comments and get proper exception and error code everywhere. Then it's time to implement the entire Lua standard library, some parts will probably be left unimplemented like parts of the debug package and coroutines might not be implemented for the 0.1.0 release. Finally I will create the test harness and hopefully find some useable test code I can bring in. And that's pretty much it for the 0.1.0 release. Full .NET integration and proper error messages/stack traces is slated for 0.2.0 and possibly 0.3.0.