6 ms·

The Lola Programming Language

25 points by komuW 5y ago

camgunz 5y ago
Love the simplicity of this language, and written in Zig!
- JohnDeHope 5y ago
  That is interesting too. Zig seems cool. I get good vibes from it. It almost makes me wish I was a systems programmer, rather than a business software programmer.
weatherlight 5y ago
1) the language looks cool, seems very easy to learn. 2) Shudders in Nobakov.
Rochus 5y ago
Name collision with https://en.wikipedia.org/wiki/Lola_(computing) https://en.wikipedia.org/wiki/Lola_(computing).
- musicale 5y ago
  I also thought this would be about Wirth's Lola (which I like as a simpler alternative to Verilog or VHDL.)
brundolf 5y ago
> 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. This seems pretty cool. Don't know if this is more common in game scripting languages, but I've never seen it before
- Rochus 5y ago
  > I've never seen it before Common e.g. in Smalltalk VMs
- jhomedall 5y ago
  Many Common Lisp implementations allow you to dump the program state to an image, which can then be loaded later.
  - neolog 5y ago
    What do they do about open file descriptors?
    - rurban 5y ago
      Store the path, position and open mode. Pipes will fail. Dynamic modules (shared libs) are also tried be re-opened.
- igouy 5y ago
  "10.4 The image file provides a frozen in time snapshot of a running Pharo system. This is the file where all objects are stored and as such it's a cross platform format. An image file contains the live state of all objects of the system (including classes and compiled methods, since they are objects too) at a given point. An image is a virtual object container." https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSuccessfulBuild/artifact/book-result/PharoTour/PharoTour.html https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExa... When the Smalltalk implementation provides lightweight processes, snapshot saves the state of the lightweight processes — so when Smalltalk is restarted, the lightweight processes restart and continue doing whatever they were doing.
  - 7373737373 5y ago
    Unfortunately, Smalltalk will never have the protection aspect simultaneously due to its global access system.
- 5y ago
b3morales 5y ago
The focus on the IR and encodability is quite interesting. If I'm understanding this FAQ item correctly > Why does the language not allow user-defined objects? it has a Lua-ish arrangement where "modules" and "objects" overlap. Seems neat. Added to my weekend reading to look more closely at the implementation.
7373737373 5y ago
These serialization and protection features are _awesome_!

25 points by komuW 5y ago

camgunz 5y ago

Love the simplicity of this language, and written in Zig!

JohnDeHope 5y ago
That is interesting too. Zig seems cool. I get good vibes from it. It almost makes me wish I was a systems programmer, rather than a business software programmer.

weatherlight 5y ago

1) the language looks cool, seems very easy to learn. 2) Shudders in Nobakov.

Rochus 5y ago

Name collision with https://en.wikipedia.org/wiki/Lola_(computing) https://en.wikipedia.org/wiki/Lola_(computing).

musicale 5y ago
I also thought this would be about Wirth's Lola (which I like as a simpler alternative to Verilog or VHDL.)

brundolf 5y ago

> 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. This seems pretty cool. Don't know if this is more common in game scripting languages, but I've never seen it before

Rochus 5y ago
> I've never seen it before Common e.g. in Smalltalk VMs
jhomedall 5y ago
Many Common Lisp implementations allow you to dump the program state to an image, which can then be loaded later.
- neolog 5y ago
  What do they do about open file descriptors?
  - rurban 5y ago
    Store the path, position and open mode. Pipes will fail. Dynamic modules (shared libs) are also tried be re-opened.
igouy 5y ago
"10.4 The image file provides a frozen in time snapshot of a running Pharo system. This is the file where all objects are stored and as such it's a cross platform format. An image file contains the live state of all objects of the system (including classes and compiled methods, since they are objects too) at a given point. An image is a virtual object container." https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSuccessfulBuild/artifact/book-result/PharoTour/PharoTour.html https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExa... When the Smalltalk implementation provides lightweight processes, snapshot saves the state of the lightweight processes — so when Smalltalk is restarted, the lightweight processes restart and continue doing whatever they were doing.
- 7373737373 5y ago
  Unfortunately, Smalltalk will never have the protection aspect simultaneously due to its global access system.
5y ago

b3morales 5y ago

The focus on the IR and encodability is quite interesting. If I'm understanding this FAQ item correctly > Why does the language not allow user-defined objects? it has a Lua-ish arrangement where "modules" and "objects" overlap. Seems neat. Added to my weekend reading to look more closely at the implementation.

7373737373 5y ago

These serialization and protection features are _awesome_!