You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oaklisp provides the ability to dump/save a world image upon exit. This is great but has two problems. First, the user must know before hand that they will want to save an image later. Second, they must essentially hard-code the name of the single, at-exit saved world file.
What is needed is the ability to save a world through a method call to a specified file without exiting the system. something like:
(save-world "myworld.bin")
A load-world would be great too but less important.
The text was updated successfully, but these errors were encountered:
That's a good idea. I don't think there's any particular technical barrier: the process could fork before doing the destructive machinations required to prepare the world for saving. We could just allocate a new bytecode instruction. Certainly this would simplify other aspects of the system, because things could be migrated out of the emulator and into user code.
Oaklisp provides the ability to dump/save a world image upon exit. This is great but has two problems. First, the user must know before hand that they will want to save an image later. Second, they must essentially hard-code the name of the single, at-exit saved world file.
What is needed is the ability to save a world through a method call to a specified file without exiting the system. something like:
(save-world "myworld.bin")
A load-world would be great too but less important.
The text was updated successfully, but these errors were encountered: