Post by @ekaitz_zarraga@mastodon.social

Ekaitz Zarraga 👹

@ekaitz_zarraga@mastodon.social · 3 weeks ago

There it is, a fresh #GNU Mes #scheme #interpreter work blog post.

This time giving more answers than questions.

https://ekaitz.elenq.tech/fasterMes7.html

Long term work is hard, dudes.

Ekaitz's tech blog

⁂

More from

Ekaitz Zarraga 👹

#interpreter #scheme #gnu

Ludovic Courtès

@civodul@toot.aquilenet.fr · 3 weeks ago

Hey @ekaitz_zarraga

Great writeup!

Note that more people care about your work than you might think. Don’t burn out, work at your own pace, and make time for yourself. I know all too well how this kind of work can be overwhelming.

Ludovic Courtès

@civodul@toot.aquilenet.fr · 3 weeks ago

@ekaitz_zarraga What you describe made me think about the Guile 1.8 → 2.0 transition: 1.8 had a “dumb” interpreter written in C, 2.0 had a simple Scheme-to-bytecode compiler and a VM.

Regarding writing the interpreter in Scheme, you may know about (ice-9 eval), which @wingo wrote about:
https://wingolog.org/archives/2009/12/09/in-which-our-protagonist-forgoes-modesty

in which our protagonist forgoes modesty — wingolog

wingolog: article: in which our protagonist forgoes modesty

Noé Lopez

@baleine@piaille.fr · 3 weeks ago

@civodul @ekaitz_zarraga @wingo Andy's posts are always a delight 😁 And a treasure full of history that would have been otherwise forgotten:

> I actually toyed with the idea of writing a hand-coded eval in VM bytecode, but I came to my senses soon enough, and the answer was delightful.