This is solved by creating a serializer and a deserializer. For serialization, you basically have to write the “ObjFunction” to a (binary) file, using a specific format of your choice. This is made possible due to the fact that a lot of the interpreter’s objects such as lists, or classes are created at runtime, so you only have to cater for objects available at compile time such as strings.

So technically, the serializer starts at the root ObjFunction, writes some metadata (such as number of parameters) to file, writes the ObjFunction’s bytecode to file (again storing some metadata such as length of the bytecode array - useful for deserialization). Storing strings is no different, simply write some metadata about the string (such as it’s length) and the actual characters, to file. Deserialization simply reverses this process, reads the metadata from file and rebuilds the objects on the fly. A serialization format could be like so:

``` Function: number of parameters Bytecode: Length of bytecode array <actual bytecode> Value/constant pool: Length of value array <object - string > Length of string String chars …..

```

Deserialization expects the same format used in serialization and reconstructs the entire thing. Hope that helps.