Earlier this year

• Oct 15, 2009

  issue 9 (No base libraries) reported by the.deathgate   -   What steps will reproduce the problem? 1. Setting up LuaInterface with Visual Studio C# Express 2008 2. Create a Lua Object 3. Create a Lua File with "print("something")" 4. Call lua file What is the expected output? What do you see instead? - I expect to see "something" on screen. - But the screen is empty. What version of the product are you using? On what operating system? - I work on Windows XP (SP2) with the LuaInterface 2.0.3 (7z-package) Please provide any additional information below. -> first I tried to call a CRL-Object with load_assembly following by import_type. I tried with "luanet." before the function call and without. Both with no result (nil object). Adding a Function from C# with RegisterFunction did do a working function call on the C#-Implementation. In the list of my linked libraries Lua52 comes with version 0.0.0.0 Might be an error in the package?

  What steps will reproduce the problem? 1. Setting up LuaInterface with Visual Studio C# Express 2008 2. Create a Lua Object 3. Create a Lua File with "print("something")" 4. Call lua file What is the expected output? What do you see instead? - I expect to see "something" on screen. - But the screen is empty. What version of the product are you using? On what operating system? - I work on Windows XP (SP2) with the LuaInterface 2.0.3 (7z-package) Please provide any additional information below. -> first I tried to call a CRL-Object with load_assembly following by import_type. I tried with "luanet." before the function call and without. Both with no result (nil object). Adding a Function from C# with RegisterFunction did do a working function call on the C#-Implementation. In the list of my linked libraries Lua52 comes with version 0.0.0.0 Might be an error in the package?
• Oct 07, 2009

  issue 8 (LuaInterface on Mono/Linux cannot load lua51.dll) reported by ulrich.buchgraber   -   What steps will reproduce the problem? 1. Take a binary + LuaInterface.dll + lua51.dll which runs correctly on .Net/Windows 2. copy them on a linux machine with mono 3. instantiate the "Lua" class What is the expected output? What do you see instead? The application terminates ans mono says: "... in assembly lua51.dll contains native code that cannot be executed by Mono on this platform" What version of the product are you using? On what operating system? I used the binaries inside "LuaInterface_2.0.3.7z" and a fresh build of LuaInterface from the subversion here. Using a Ubuntu 9.04 x86 Linux.

  What steps will reproduce the problem? 1. Take a binary + LuaInterface.dll + lua51.dll which runs correctly on .Net/Windows 2. copy them on a linux machine with mono 3. instantiate the "Lua" class What is the expected output? What do you see instead? The application terminates ans mono says: "... in assembly lua51.dll contains native code that cannot be executed by Mono on this platform" What version of the product are you using? On what operating system? I used the binaries inside "LuaInterface_2.0.3.7z" and a fresh build of LuaInterface from the subversion here. Using a Ubuntu 9.04 x86 Linux.
• Sep 15, 2009

  issue 4 (Error info should include the line number) changed by capresti   -   Fixed in r14, please verify

  Status: Fixed

  Owner: capresti

  Fixed in r14, please verify

  Status: Fixed

  Owner: capresti
• Sep 15, 2009

  r14 (Further fixes from Bastian: - Added IsExecuting variable to ...) committed by capresti   -   Further fixes from Bastian: - Added IsExecuting variable to Lua - Fix for error info inclusion of line number ( Issue #4 )

  Further fixes from Bastian: - Added IsExecuting variable to Lua - Fix for error info inclusion of line number ( Issue #4 )
• Sep 11, 2009

  issue 5 (LoadString and LoadFile leak data on the lua stack) Status changed by capresti   -   Fixed in r13

  Status: Fixed

  Fixed in r13

  Status: Fixed
• Sep 11, 2009

  r13 (Merged contributions from Bastian Eicher: - Preserved stack ...) committed by capresti   -   Merged contributions from Bastian Eicher: - Preserved stack trace on .NET exceptions - Added support for attribute based registration of methods - Global object tracking for auto completion providers Merged fix for Issue #5

  Merged contributions from Bastian Eicher: - Preserved stack trace on .NET exceptions - Added support for attribute based registration of methods - Global object tracking for auto completion providers Merged fix for Issue #5
• Sep 11, 2009

  issue 5 (LoadString and LoadFile leak data on the lua stack) changed by capresti   -  

  Status: Started

  Owner: capresti

  Status: Started

  Owner: capresti
• Sep 11, 2009

  issue 6 (Missing Strong-Name on Library) changed by capresti   -  

  Status: Accepted

  Owner: capresti

  Labels: Type-Enhancement −Type-Defect

  Status: Accepted

  Owner: capresti

  Labels: Type-Enhancement −Type-Defect
• Sep 11, 2009

  issue 7 (Not able to access Interface) commented on by b.karwacki   -   It seems to me you do not have lua51.dll (native library used by luainterface.dll) in your application's directory. Simply adding .NET dll as a reference is NOT enough. If you do, try to change Platform Target in build options to x86.

  It seems to me you do not have lua51.dll (native library used by luainterface.dll) in your application's directory. Simply adding .NET dll as a reference is NOT enough. If you do, try to change Platform Target in build options to x86.
• Sep 06, 2009

  issue 7 (Not able to access Interface) commented on by Jason.A.Bentley   -   using System; using System.Collections.Generic; using System.Linq; using System.Text; using LuaInterface; namespace ConsoleApplication1 { class Program { public static Lua pLuaVM = null; static void Main(string[] args) { Console.WriteLine("Hello, world!"); pLuaVM = new Lua(); Console.ReadLine(); } } }

  using System; using System.Collections.Generic; using System.Linq; using System.Text; using LuaInterface; namespace ConsoleApplication1 { class Program { public static Lua pLuaVM = null; static void Main(string[] args) { Console.WriteLine("Hello, world!"); pLuaVM = new Lua(); Console.ReadLine(); } } }
• Sep 06, 2009

  issue 7 (Not able to access Interface) reported by Jason.A.Bentley   -   I'm attempting to use Lua with C# 1. I have the latest version C# Express 2208 2. I downloaded "LuaInterface 2.0.3 Released" and extracted it to folder 3. I created a simple C# "Hello World" that works fine. 4. I added "using LuaInterface;" to the project 5. This threw an error: "The type or namespace 'LuaInterface' could not be found" 6. "Project/Add Reference/Browse" 7. "Hello World" works again. 8. Added "public static Lua pLuaVM = null;" to the Class 9. This works fine 10. Added "pLuaVM = new Lua();" to the Main 11. Error "Could not load file or assembly 'lua51, Version=0.0.0.0, Culture=neutral, PublicKeyToken=1e1fb15b02227b8a' or one of its dependencies. An attempt was made to load a program with an incorrect format." What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below.

  I'm attempting to use Lua with C# 1. I have the latest version C# Express 2208 2. I downloaded "LuaInterface 2.0.3 Released" and extracted it to folder 3. I created a simple C# "Hello World" that works fine. 4. I added "using LuaInterface;" to the project 5. This threw an error: "The type or namespace 'LuaInterface' could not be found" 6. "Project/Add Reference/Browse" 7. "Hello World" works again. 8. Added "public static Lua pLuaVM = null;" to the Class 9. This works fine 10. Added "pLuaVM = new Lua();" to the Main 11. Error "Could not load file or assembly 'lua51, Version=0.0.0.0, Culture=neutral, PublicKeyToken=1e1fb15b02227b8a' or one of its dependencies. An attempt was made to load a program with an incorrect format." What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below.
• Aug 05, 2009

  r12 (- Improved Metatables getMethod when working with float[], d...) committed by capresti   -   - Improved Metatables getMethod when working with float[], double[], int[] arrays and attempting to index them

  - Improved Metatables getMethod when working with float[], double[], int[] arrays and attempting to index them
• Jul 20, 2009

  issue 6 (Missing Strong-Name on Library) reported by sanderge...@home.nl   -   The fact that the LuaInterface library (and the lua library) aren't signed annoys me. Because they aren't signed I can't use them in any project which requires assemblies to be signed. I could recompile both libraries myself, but it's not bad practice to sign an assembly you are distributing (even if you don't need it yourself)

  The fact that the LuaInterface library (and the lua library) aren't signed annoys me. Because they aren't signed I can't use them in any project which requires assemblies to be signed. I could recompile both libraries myself, but it's not bad practice to sign an assembly you are distributing (even if you don't need it yourself)
• Jun 15, 2009

  issue 5 (LoadString and LoadFile leak data on the lua stack) reported by Byronholldorf   -   What steps will reproduce the problem? 1. Use LoadString or LoadFile thousands of times. Program should complete successfully regardless of number of calls to LoadString/LoadFile. Instead, the Lua stack overflows. Using LuaInterface 2.0.3 on VC9, WinXP. The following modification appears to work for every test case I've thrown at it so far, but, I'm not a lua expert. I Changed LoadString in Lua.cs:238 to pop values off the stack before returning: public LuaFunction LoadString(string chunk, string name) { int oldTop = LuaDLL.lua_gettop(luaState); if (LuaDLL.luaL_loadbuffer(luaState, chunk, name) != 0) ThrowExceptionFromError(oldTop); LuaFunction result = translator.getFunction(luaState, -1); translator.popValues(luaState, oldTop); return result; } I made a similar modification to LoadFile.

  What steps will reproduce the problem? 1. Use LoadString or LoadFile thousands of times. Program should complete successfully regardless of number of calls to LoadString/LoadFile. Instead, the Lua stack overflows. Using LuaInterface 2.0.3 on VC9, WinXP. The following modification appears to work for every test case I've thrown at it so far, but, I'm not a lua expert. I Changed LoadString in Lua.cs:238 to pop values off the stack before returning: public LuaFunction LoadString(string chunk, string name) { int oldTop = LuaDLL.lua_gettop(luaState); if (LuaDLL.luaL_loadbuffer(luaState, chunk, name) != 0) ThrowExceptionFromError(oldTop); LuaFunction result = translator.getFunction(luaState, -1); translator.popValues(luaState, oldTop); return result; } I made a similar modification to LoadFile.
• May 22, 2009

  r11 (- Added support for generic methods (note: does not support ...) committed by capresti   -   - Added support for generic methods (note: does not support generic methods in generic classes)

  - Added support for generic methods (note: does not support generic methods in generic classes)
• May 21, 2009

  issue 4 (Error info should include the line number) commented on by qrli36   -   Sorry, just checked my code, it is not in ThrowExceptionFromError() but in ObjectTranslator.throwError(). The old code is still there. The thing I added is to also provide chunck name and line number for Exceptions raised from .NET side. It's like this: internal void throwError(IntPtr luaState,object e) { // If the argument is a mere string, we are free to add extra info to it (as opposed to some private C# exception object or somesuch, which we just pass up) // We use this to remove anything pushed by luaL_where int oldTop = LuaDLL.lua_gettop(luaState); // Stack frame #1 is our C# wrapper, so not very interesting to the user // Stack frame #2 must be the lua code that called us, so that's what we want to use LuaDLL.luaL_where(luaState, 1); object[] curlev = popValues(luaState, oldTop); // Debug.WriteLine(curlev); string errLocation = ""; if (curlev.Length > 0) errLocation = curlev[0].ToString(); if (e is string) e = errLocation + e; else if (e is Exception) { Exception ex = e as Exception; Exception luaex = new ApplicationException(errLocation + ex.Message, ex); e = luaex; } push(luaState,e); LuaDLL.lua_error(luaState); } Here the use of ApplicationException should be a bad idea. I just wrote it to make a quick working build.

  Sorry, just checked my code, it is not in ThrowExceptionFromError() but in ObjectTranslator.throwError(). The old code is still there. The thing I added is to also provide chunck name and line number for Exceptions raised from .NET side. It's like this: internal void throwError(IntPtr luaState,object e) { // If the argument is a mere string, we are free to add extra info to it (as opposed to some private C# exception object or somesuch, which we just pass up) // We use this to remove anything pushed by luaL_where int oldTop = LuaDLL.lua_gettop(luaState); // Stack frame #1 is our C# wrapper, so not very interesting to the user // Stack frame #2 must be the lua code that called us, so that's what we want to use LuaDLL.luaL_where(luaState, 1); object[] curlev = popValues(luaState, oldTop); // Debug.WriteLine(curlev); string errLocation = ""; if (curlev.Length > 0) errLocation = curlev[0].ToString(); if (e is string) e = errLocation + e; else if (e is Exception) { Exception ex = e as Exception; Exception luaex = new ApplicationException(errLocation + ex.Message, ex); e = luaex; } push(luaState,e); LuaDLL.lua_error(luaState); } Here the use of ApplicationException should be a bad idea. I just wrote it to make a quick working build.
• May 20, 2009

  issue 4 (Error info should include the line number) commented on by capresti   -   Hmm, I'm not sure why it is missing to be honest. Care to submit a patch or paste your changes here and ill merge back in?

  Hmm, I'm not sure why it is missing to be honest. Care to submit a patch or paste your changes here and ill merge back in?
• May 06, 2009

  issue 4 (Error info should include the line number) reported by qingrui.li   -   The previous 2.0 can provide chunk name and line number in error string when a lua parsing error occurs, but not when an exception is thrown from .NET code. I looked through the code and found that in ThrowExceptionFromError(), it only gets the chunk name and line number and adds them to the error string for lua errors but not for .NET exceptions. I tried to modify it so that it also extracts the chunk name and line number for the error when the error is a .NET exception, and it works great. It helps a lot for me to find where exactly the error occurs in lua source code. In the 2.0.3 release, I saw the code which fetch the chunk name and line number information is missing. Why? I think it is great to always have those information.

  The previous 2.0 can provide chunk name and line number in error string when a lua parsing error occurs, but not when an exception is thrown from .NET code. I looked through the code and found that in ThrowExceptionFromError(), it only gets the chunk name and line number and adds them to the error string for lua errors but not for .NET exceptions. I tried to modify it so that it also extracts the chunk name and line number for the error when the error is a .NET exception, and it works great. It helps a lot for me to find where exactly the error occurs in lua source code. In the 2.0.3 release, I saw the code which fetch the chunk name and line number information is missing. Why? I think it is great to always have those information.
• Mar 08, 2009

  issue 3 (Randon error when parse big tables) commented on by capresti   -   Thanks all, I'd guess it to be the dispose fixes in the LuaFunction, LuaTable, LuaUserData that made the difference. Is someone able to verify the fix on the new 2.0.3 release?

  Thanks all, I'd guess it to be the dispose fixes in the LuaFunction, LuaTable, LuaUserData that made the difference. Is someone able to verify the fix on the new 2.0.3 release?
• Mar 08, 2009

  changelog (Full changelog for all releases) Wiki page edited by capresti
• Mar 08, 2009

  changelog (Full changelog for all releases) Wiki page added by capresti
• Mar 08, 2009

  Downloads (Current release: LuaInterface 2.0.3) Wiki page edited by capresti
• Mar 08, 2009

  Downloads (Current release: LuaInterface 2.0.3) Wiki page added by capresti
• Mar 08, 2009

  LuaInterface_2.0.3.7z (LuaInterface 2.0.3) file uploaded by capresti   -  

  Labels: Featured

  Labels: Featured
• Mar 08, 2009

  issue 2 (DoString() is better to have an overload with the chunkName ...) Status changed by capresti   -  

  Status: Fixed

  Status: Fixed
• Mar 08, 2009

  issue 2 (DoString() is better to have an overload with the chunkName ...) commented on by capresti   -   Implemented in r6

  Implemented in r6
• Mar 07, 2009

  r6 (- Added a check for a passed state on Close - Added overload...) committed by capresti   -   - Added a check for a passed state on Close - Added overloaded DoString - Added some more test cases

  - Added a check for a passed state on Close - Added overloaded DoString - Added some more test cases
• Jan 27, 2009

  issue 3 (Randon error when parse big tables) commented on by mascarenhas   -   Hi, Craig, Carlos Eduardo above came to me a few days ago with this issue, but the code in the SVN HEAD seems to have solved it (I can reproduce it with the dlls they sent me, dated 07/20/2008, but not with the freshy compiled dlls I am attaching to this note). Without having the change history prior to the Google Code checking it's hard to know what actually solved it. :-)

  Hi, Craig, Carlos Eduardo above came to me a few days ago with this issue, but the code in the SVN HEAD seems to have solved it (I can reproduce it with the dlls they sent me, dated 07/20/2008, but not with the freshy compiled dlls I am attaching to this note). Without having the change history prior to the Google Code checking it's hard to know what actually solved it. :-)
• Jan 21, 2009

  issue 3 (Randon error when parse big tables) commented on by carloseduardo.gc   -   This error also occurs to me. Also to process large tables. This error occurs on two machines: Apparently the error does not occur in a single core machines. PC1: Athlon 64 X2 4000+ com Windows XP 64 bits PC2: Intel Core 2 Duo 6000 com Windows XP 32 bits Attach the exit of TestLua.exe

  This error also occurs to me. Also to process large tables. This error occurs on two machines: Apparently the error does not occur in a single core machines. PC1: Athlon 64 X2 4000+ com Windows XP 64 bits PC2: Intel Core 2 Duo 6000 com Windows XP 32 bits Attach the exit of TestLua.exe

Older

• Dec 26, 2008

  issue 2 (DoString() is better to have an overload with the chunkName ...) commented on by qingrui.li   -   Yes, that's what I mean. When lua throws an error, it provides the location in [chunkName:lineNumber] format, and it helps to debug lua script. But if the script is run by DoString(), there will be no meaningful chunkName. In some cases, I'd like to pass a name instead of the default behavior.

  Yes, that's what I mean. When lua throws an error, it provides the location in [chunkName:lineNumber] format, and it helps to debug lua script. But if the script is run by DoString(), there will be no meaningful chunkName. In some cases, I'd like to pass a name instead of the default behavior.
• Dec 26, 2008

  issue 1 (bug in LuaDLL::luaL_loadbuffer causing parsing error for lua...) commented on by qingrui.li   -   I did that too. It works

  I did that too. It works
• Dec 23, 2008

  issue 1 (bug in LuaDLL::luaL_loadbuffer causing parsing error for lua...) changed by capresti   -   I made the change using strlen(cs1), can you verify this works as expected or otherwise suggest a better way?

  Status: Fixed

  Owner: capresti

  I made the change using strlen(cs1), can you verify this works as expected or otherwise suggest a better way?

  Status: Fixed

  Owner: capresti
• Dec 23, 2008

  r5 (- Fix for issue #1) committed by capresti   -   - Fix for issue #1

  - Fix for issue #1
• Dec 23, 2008

  issue 2 (DoString() is better to have an overload with the chunkName ...) Owner changed by capresti   -   Im not sure I follow here...are you referring to the DoString in Lua.cs public object[] DoString(string chunk)? Can you give a little more info please?

  Owner: capresti

  Im not sure I follow here...are you referring to the DoString in Lua.cs public object[] DoString(string chunk)? Can you give a little more info please?

  Owner: capresti
• Dec 23, 2008

  issue 3 (Randon error when parse big tables) reported by freemanru   -   1. Create in somfile.lua table with field's count more then 100 and with embeded tables. 2. Create new lua class in C#, then DoFile("somfile.lua") and try to parse the table. 3. In random place we got some exceptions - place amd exeptions every time is defferent. 4. Some intrecting - in Debug mode of VS, we can run application after exeptions is raised just to run "Continie" command in debuger. After raise eror and continie table parsed correct. 5. Small tables parsed without errors. Exceptions example: 1: unprotected error in call to Lua API (arg_value3570index3568 value) in LuaInterface.Lua.PanicCallback(IntPtr luaState) in LuaInterface.LuaDLL.lua_gettable(IntPtr luaState, Int32 index) in LuaInterface.Lua.getObject(String[] remainingPath) in LuaInterface.Lua.getObject(Int32 reference, String field) in LuaInterface.LuaTable.get_Item(String field) 2: AccessViolationExeption in LuaInterface.LuaDLL.luaL_ref(IntPtr luaState, Int32 registryIndex) in LuaInterface.LuaDLL.lua_ref(IntPtr luaState, Int32 lockRef) in LuaInterface.ObjectTranslator.getTable(IntPtr luaState, Int32 index) in LuaInterface.ObjectTranslator.getObject(IntPtr luaState, Int32 index) in LuaInterface.Lua.getObject(String[] remainingPath) in LuaInterface.Lua.getObject(Int32 reference, String field) in LuaInterface.LuaTable.get_Item(String field) 3: NullReferenceExeption

  1. Create in somfile.lua table with field's count more then 100 and with embeded tables. 2. Create new lua class in C#, then DoFile("somfile.lua") and try to parse the table. 3. In random place we got some exceptions - place amd exeptions every time is defferent. 4. Some intrecting - in Debug mode of VS, we can run application after exeptions is raised just to run "Continie" command in debuger. After raise eror and continie table parsed correct. 5. Small tables parsed without errors. Exceptions example: 1: unprotected error in call to Lua API (arg_value3570index3568 value) in LuaInterface.Lua.PanicCallback(IntPtr luaState) in LuaInterface.LuaDLL.lua_gettable(IntPtr luaState, Int32 index) in LuaInterface.Lua.getObject(String[] remainingPath) in LuaInterface.Lua.getObject(Int32 reference, String field) in LuaInterface.LuaTable.get_Item(String field) 2: AccessViolationExeption in LuaInterface.LuaDLL.luaL_ref(IntPtr luaState, Int32 registryIndex) in LuaInterface.LuaDLL.lua_ref(IntPtr luaState, Int32 lockRef) in LuaInterface.ObjectTranslator.getTable(IntPtr luaState, Int32 index) in LuaInterface.ObjectTranslator.getObject(IntPtr luaState, Int32 index) in LuaInterface.Lua.getObject(String[] remainingPath) in LuaInterface.Lua.getObject(Int32 reference, String field) in LuaInterface.LuaTable.get_Item(String field) 3: NullReferenceExeption
• Nov 29, 2008

  r4 (- added functionality to class Lua and LuaDLL for LuaInterfa...) committed by rostermeier   -   - added functionality to class Lua and LuaDLL for LuaInterfaceDebugger - Bugfix in ldo.c: structure lua_debug was not initialized completely which caused the .net marshaller to crash

  - added functionality to class Lua and LuaDLL for LuaInterfaceDebugger - Bugfix in ldo.c: structure lua_debug was not initialized completely which caused the .net marshaller to crash
• Nov 19, 2008

  issue 2 (DoString() is better to have an overload with the chunkName ...) reported by qingrui.li   -   The current DoString() use the parameter source code string as both source string and chunkName, which cause the chunkName to be very long and useless. It is bette to add an overload with a chunkName parameter, so that the error info thrown out from lua has meaningful chunkName which can help debugging.

  The current DoString() use the parameter source code string as both source string and chunkName, which cause the chunkName to be very long and useless. It is bette to add an overload with a chunkName parameter, so that the error info thrown out from lua has meaningful chunkName which can help debugging.
• Nov 19, 2008

  issue 1 (bug in LuaDLL::luaL_loadbuffer causing parsing error for lua...) reported by qingrui.li   -   In this method, the ::luaL_loadbuffer call should use the length of cs1 but not buff->Length, because buff->Length is smaller than the bytes count when the string contains MBCS characters, and thus cause lua parse error. static int luaL_loadbuffer(IntPtr luaState, String^ buff, String^ name) { char *cs1 = (char *) Marshal::StringToHGlobalAnsi(buff).ToPointer(); char *cs2 = (char *) Marshal::StringToHGlobalAnsi(name).ToPointer(); // this line is wrong! int result = ::luaL_loadbuffer(toState, cs1, buff->Length, cs2); Marshal::FreeHGlobal(IntPtr(cs1)); Marshal::FreeHGlobal(IntPtr(cs2)); return result; }

  In this method, the ::luaL_loadbuffer call should use the length of cs1 but not buff->Length, because buff->Length is smaller than the bytes count when the string contains MBCS characters, and thus cause lua parse error. static int luaL_loadbuffer(IntPtr luaState, String^ buff, String^ name) { char *cs1 = (char *) Marshal::StringToHGlobalAnsi(buff).ToPointer(); char *cs2 = (char *) Marshal::StringToHGlobalAnsi(name).ToPointer(); // this line is wrong! int result = ::luaL_loadbuffer(toState, cs1, buff->Length, cs2); Marshal::FreeHGlobal(IntPtr(cs1)); Marshal::FreeHGlobal(IntPtr(cs2)); return result; }
• Oct 16, 2008

  r3 (- Implemented a basic fix for issues with indexers (multiple...) committed by capresti   -   - Implemented a basic fix for issues with indexers (multiple indexers on an object, indexers with values the same as a property name of the object)

  - Implemented a basic fix for issues with indexers (multiple indexers on an object, indexers with values the same as a property name of the object)
• Sep 08, 2008

  r2 (Initial checkin) committed by capresti   -   Initial checkin

  Initial checkin
• Aug 20, 2008

  Project luainterface created by capresti   -   A library for integration between the Lua language and Microsoft .NET platform's Common Language Runtime (CLR)

  A library for integration between the Lua language and Microsoft .NET platform's Common Language Runtime (CLR)