Today I tried to use make-log-based-eval rather than the normal make-base-eval.
The logging version logs the result of an evaluation: it write the serialized value to a file.
When replayed the value is deserialized from disk.
Sounds easy enough, so I added the property prop:serializable to the obj struct.
The obj struct represents a Python object and consist of the name of the object class and a C-pointer to the Python object.
Serializing the name only gets me to this result (using replay):
Compare this to the original:
The missing part is stored in the Python object.
Now Python also have (de)serialization called pickling and unpickling.
But ... that can't be used, since the reason we are doing this is to build the documentation
on a machine without Python.
The idea of logging the evaluation results are good, but the logging happens too early.
What is needed is a logging version of examples where the scribble structures is logged.
At least I think so - but maybe I am missing an alternative solution?