Problems with conditionally loaded libraries about eris HOT 4 CLOSED

That is indeed deliberate, because Eris can't (or rather shouldn't [IMHO]) decide on its own what to do if values it needs for unpersisting a state are missing, following the principle of least surprise.

If the values exposed in debug mode are all functions you can take the lazy approach: slap a setmetatable(uperms, {__index=function()return function()end end}) on your permanent value table, automatically returning a dummy function for all missing values.

The cleaner, but more verbose approach would be to manually provide the same values you have in debug mode in the permanent value table, but have them do nothing (i.e. have all functions be dummy functions, all numbers be 0xDEADBEEF, all strings be "debug only" or something).

Alternatively, assuming that wouldn't break things left-and-right anyway, a new setting might be an option, controlling Eris' behavior on missing permanent values (error - the current behavior - or replace the value with nil; non-nil values would still have to be handled via __index, e.g.).

from eris.

If the values exposed in debug mode are all functions...

They are not, they are lua tables though. But just pushing empty tables did not do the trick, the problem was the same:

lua_newtable(m_L); lua_setglobal(m_L, "package");
lua_newtable(m_L); lua_setglobal(m_L, "io");
lua_newtable(m_L); lua_setglobal(m_L, "os");

any more ideas?

from eris.

Sounds very much like what I described here. You'll probably have to add the actual functions to the perms table, not just the table containing them.

from eris.

mmh.. that is what I've thought. I decided to just remove this conditional loading of libraries. I never had any use for them in the last year anyways, so they are probably not as useful. Thanks for your explanations!

from eris.