> The LoLa runtime is designed to be saved to disk at any point not executing any code. This means that you can let your script execute for 1000 instructions, save the runtime state to disk and resume execution a week later on another computer, not having any problems with script resumption. This is especially useful for games which often want to embed the state of their scripts into the save files.<p>This seems pretty cool. Don't know if this is more common in game scripting languages, but I've never seen it before
Name collision with <a href="https://en.wikipedia.org/wiki/Lola_(computing)" rel="nofollow">https://en.wikipedia.org/wiki/Lola_(computing)</a>.
The focus on the IR and encodability is quite interesting. If I'm understanding this FAQ item correctly<p>> Why does the language not allow user-defined objects?<p>it has a Lua-ish arrangement where "modules" and "objects" overlap.<p>Seems neat. Added to my weekend reading to look more closely at the implementation.