Internals of eris

[fnuecke]

Internals of eris

[fnuecke]

Always happy to hear when it's helpful to people :)

I'm afraid there's no article specifically discussing the internals of Eris. Aside from the readme on the repo describing the high-level functionality, the file format documentation is probably the most you can find before having to dig into the actual code.

Aside from details though, basically what happens is that persist_typed is called starting with a root object to persist, and then possibly called recursively while traversing all references leading out from that root object -- so for tables all their keys and values, for functions their upvalues, for threads their stack etc. For deserialization it's the opposite process.

One thing that will help immensely while reading the code is understanding what the comments on the right of many lines mean: e.g. in this line, it's /* ... tbl nil */. These comments document the state of the Lua stack after that line finished execution. So here the stack holds some values (...), a table (tbl) and a nil value (nil), which was just pushed onto the stack.

If you have any specific questions, let me know and I'll try to remember the answers to them.

[alex-aparin]

Great thanks for reply (I have understood something from your code) . I will definitely ask questions (I need some time to learn sources of eris).