lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Tue, Sep 20, 2016 at 4:01 PM, Christian N. <> wrote:

> I fail to see how this is a problem. If I link my MSVC-compiled program with a MinGW-compiled lua53.dll, I might get the following dependency tree (swap msvcrt.dll with msvcr120.dll for the reverse case):

First, the reliance on msvcrt.dll is a problem with MinGW in general, not just with Lua built with MinGW.

Second, a problem with using different runtimes is that those runtimes may each assume they are the only runtime, with disastrous consequences.

Third, there is the problem of passing "objects" created in one runtime to another one, as mentioned by others earlier, even though I do not think it affects Lua.

Fourth, multiple libraries that work well with one runtime may fail to work when they use multiple runtimes even in salutations not covered by #3, because they will not have a common global state in their runtimes. E.g., if some C code wants to communicate with some Lua code via the environment, this may or may not work unpredictably if runtimes are allowed to be different.