Re: Yet another reason to crash with multiple Lua runtime?

[Shmuel Zeigerman <shmuz@...>]

Luiz Henrique de Figueiredo wrote:
> This is well known and has been mentioned in the archives. The answer of
> course is make sure not to link more than one Lua core into your app!

Though I won't argue with the above statement, there's a case when it'd 
be desirable to be able to have 2 Lua cores.

I have an app (named lua51x.exe) that is a static build of Lua 5.1 with 
several libraries also linked statically into this executable. So this 
executable has no dependencies other than Windows system libraries 
available on any modern Windows installation, therefore it always works 
"out-of-the-box". However, I'd like it to be able to require() 
additional Lua libraries (that are not built into it).

An interesting thing is that Lua 5.1 is almost there. If I don't 
require() 'strict', then lua51x.exe runs happily test suites for all the 
Lua libraries on my system. This makes me think that fixing the 
dummynode_ issue is worthwhile.

--
Shmuel