A Lua implementation for the Dynamic Language Runtime (DLR).
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
ExtTest
NeoCmd Fix: Project Url Aug 2, 2018
NeoLua.Dbg Chg: Update DLR Apr 19, 2017
NeoLua.MSBuild Merge: Portable to Master Jun 11, 2015
NeoLua.NuGet Chg: nuget upload uri Feb 28, 2018
NeoLua.Test Implement math.frexp and math.ldexp (#72) May 4, 2018
NeoLua Fix: Project Url Aug 2, 2018
NeoLuaD Fix: date and time functions (#75) Aug 13, 2018
NeoSpeed
VBtest Fix: VB compatibility Mar 8, 2016
doc Implement math.frexp and math.ldexp (#72) May 4, 2018
packages New: Manipulating closures/upvalues Oct 27, 2014
.gitignore Chg: nuget ApiKey handling Feb 27, 2018
ISSUE_TEMPLATE.md Add: issue template Oct 20, 2017
LICENSE.md Create LICENSE.md Nov 13, 2014
LuaDLR.sln Fix: Project Url Aug 2, 2018
LuaDLR.vssscc Erste Import Sep 29, 2013
README.md Chg: Readme.md - removed iOS (#33) +, Refectoring Oct 17, 2016

README.md

NeoLua

A Lua implementation for the Dynamic Language Runtime (DLR).

Introduction

NeoLua is an implementation of the Lua language. Currently, the implementation is on the level of Lua_5.3 (http://www.lua.org/manual/5.3/manual.html). The goal is to follow the reference of the C-Lua implementation and combine this with full .NET Framework support. That means, it should be easy to call .NET functions from Lua and it should be easy access variables and functions from a .net language (e.g. C#, VB.NET, ...).

NeoLua is implemented in C# and uses the Dynamic Language Runtime. It therefore integrates very well with the .net framework.

Quickstart

You can play and test the language with the tool NeoCmd.

NeoCmd

Or there are two easy ways to use NeoLua in your project.

  • Download the Neo.Lua.dll and add the reference. For full desktop support also a reference to Neo.Lua.Desktop.dll is useful.
  • Install the NuGet-Package of NeoLua.

Simple example:

using (Lua l = new Lua()) // create the lua script engine
{
  dynamic g = l.CreateEnvironment(); // create a environment
  g.dochunk("a = 'Hallo World!';", "test.lua"); // create a variable in lua
  Console.WriteLine(g.a); // access a variable in c#
  g.dochunk("function add(b) return b + 3; end;", "test.lua"); // create a function in lua
  Console.WriteLine("Add(3) = {0}", g.add(3)); // call the function in c#
}
Using l As Lua = New Lua ' create the lua script engine
    Dim g As Object = l.CreateEnvironment(Of LuaGlobal)() ' create a environment
    g.dochunk("a = 'Hallo World!';", "test.lua") ' create a variable in lua
    Console.WriteLine(g.a) ' access a variable in VB
    g.dochunk("function add(b) return b + 3; end;", "test.lua") ' create a function in lua
    Console.WriteLine("Add(3) = {0}", (New LuaResult(g.add(3)))(0)) ' call the function in VB
End Using

A more "complex" script, that shows the interaction between lua and .net:

local t = clr.System.Int32[](6, 8, 9, 19);",
return t:Sum(), t:Where(function(c : int) : bool return c < 10 end):Sum()

NeoLua is a .net portable assembly (IL) for

  • .net framework 4.5.1
  • Windows Phone 8.1
  • Windows Store Apps 8.1
  • Xamarin.Android

There will be no support for .net frameworks lower than 4.5.

It does not work with

  • Xamarin.iOS. and every .net runtime that does not support code generation.

What NeoLua is useful for

  • Outsource the logic of your application into scripts
  • Structuring of logic
  • Build a dynamic configuration system, with functions and variables
  • As a formula parser
  • ...

So, this could be reliable partner for your compiled .NET application or engine (e.g. Game Engines).

What I did not have in mind

  • Compiling libraries
  • Standalone applications

Advantages of NeoLua

  • Dynamic access between Lua script and and the host application/.NET framework and vice-versa.
  • NeoLua is based on the DLR. So you get compiled code that is collectable and well-optimized.
  • It is compatible with the .NET world (e.g. C#, VB.NET, IronPython, ...).
  • Full and easy access to the .NET framework or your own libraries (with no stub code).
  • A rich implementation of the lua table, for a got integration in the .net world e.g. Binding, Enumeration, ...
  • A .NET Framework Garbage Collector that is well-tested and very fast.
  • Pure IL (x86,x64 support)

Drawbacks of NeoLua

  • It is not 100% compatible to Lua. But I will try very hard.
  • No deployment of precompiled scripts.

Drawbacks of bridges to c-lua, that are solved with NeoLua

  • You have two memory managers and so you have to marshal every data between these two worlds. That takes time and there are a lot pitfalls to get memory leaks.
  • C-Lua interprets its own bytecode. The code is not compiled to machine code.

Documentation

This documention has the same structure like the official reference (Lua 5.3), so it should be easy to compare the two worlds.

  1. Introduction
  2. Basic concepts
  3. Language
  4. Application Program Interface
    1. Getting started
    2. Script engine
    3. Chunks
    4. Table's
  5. The Auxiliary Library
    1. clr library
    2. Extent lua table
    3. Debugging
  6. Standard libraries
  7. NeoCmd

If there is something unclear, wrong or misunderstanding please use the discussions.

Links