Dynamic options

[fnuecke]

Dynamic options

[SirVer]

I would prefer to have a persist_with_perms(perms, table, options) method instead of having perms being mandatory or overloading persist()s first parameter in any way.

[fnuecke]

I agree that the mandatory perms part sucks. I'm thinking an alternative might be to just store the options in the registry (and possibly copy them to the info structs used when persisting/unpersisting for performance). So there'd be one more function, eris.settings([table]) - or a couple of getters/setters. On the C side I imagine passing the argument via the Lua stack might also be nice, to avoid having more functions for configuring than for persisting...

[fnuecke]

Some notes:

• all settings are stored in the registry (if set), so they will be separate for different Lua states but shared among all coroutines; I think this is a good compromise between implementation complexity and context isolation.
• all settings can be changed from the Lua side. Create a wrapper with the original function as a local variable / upvalue to control access - although that's probably an unlikely scenario, since you'd never want to expose Eris to unsafe code, because eris.unpersist() is utterly unsafe as it can load compiled byte code (function prototypes).

Also, if someone finds data-structures that segfault with the default value of maxrec, please let me know (and also let me know the highest safe value so this can be made the new default). Thanks.