Thanks. I have considered that too. However, because
of the VC runtime nightmare, I was thinking of having
the problem solve once and for all and opt for the
.NET integration.
For those who is interested, after dropping back to an
older version of LuaInterface, I achieved half of what
I want, from CLR -> Lua(full access of C modules) ->
CLR.
Though not pure Lua -> CLR.
I find this a pretty nice solution on Windows. I can
write Windows application in C#/VB.NET/IronPython and
use Lua for the guts. Sure I can use IronPython too
but IronPython cannot use C modules of CPython.
I am waiting for the new LuaCLR which sounds very
interesting too.
--- Ross Berteig <Ross@CheshireEng.com> wrote:
As a shameless plug, and a reminder to myself to
push the
project along, you might want to see of Lua Windows
Service
(http://luaforge.net/projects/luaservice/) does what
you
need.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
