miniblog.

← Back to all posts
May 3, 2014 at 11:05
I've rewritten the eval() of Trifle lisp to use a stack: https://github.com/Wilfred/trifle/pull/3 It was an adventure, and highly educational!
Don't use recursion for evaluation. by Wilfred · Pull Request #3 · Wilfred/trifle
Don't use recursion for evaluation. by Wilfred · Pull Request #3 · Wilfred/trifle
Using recursion during evaluation is a problem. A recursive program (or deeply nested program) may cause a stack overflow in the interpreter. It prevents us adding TCO later. We cannot allow users ...

Related Posts

Mar 16, 2025 at 23:30
36
Is there any relationship between language adoption and the size of its standard library? These days it seems completely orthogonal, but early Java adopters spoke highly of the collections library compared with C++. Maybe it's the widespread availability of package managers?
Jun 22, 2019 at 22:35
The US Navy is exploring ships that are more highly automated. The crew is smaller, and their roles are generalist problem solvers.
At Work, Expertise Is Falling Out of Favor
At Work, Expertise Is Falling Out of Favor
These days, it seems, just about all organizations are asking their employees to do more with less. Is that actually a good idea?
Jan 15, 2018 at 00:29
Yes, highly optimising compilers can be less predictable. But given the choice between two compilers, where one is easier to reason about but the other produces faster overall code, I'd pick the latter every time.