attempt to persist a light C function? about eris

[fnuecke]

I'm glad if it helps!

What you're probably seeing is the environment your closures are created in being stored as an upvalue of that closure - that environment probably being _G, and therefore containing a bunch of C functions. A quick solution for this (and in most cases a good idea anyway) is to simply throw _G into the permanent values.

In general, I'd recommend eris.settings("path", true) when debugging, in which case it'll tell you exactly where it failed (see the last section in the readme).

Since it can happen that C functions from the global environment are stored somewhere else, directly (e.g. local variables or as upvalues), it can make sense to automatically populate the permanent value table with whatever functions there are in the global environment (directly or indirectly). Here's a snippet that does this, lines 34-67, if you're interested. I've been using this approach (though implemented on the 'host' side) very successfully.

[krisr]

Thanks so much for the quick reply. Yes, I worked around this exactly as you suggested, but I didn't know about eris.settings("path..., that will be very helpful. I will play around with your snippet as well.

I'm using eris to build a stateful UI library on top of cocoa for my game development tools. It's really neat to be able to launch a handful of new 3D views and slider panels, quit to tweak some C++ rendering code, and relaunch with the exact same UI and views I had.

[fnuecke]

Happy to help. That's a pretty cool use-case, good luck with it!