simon/post-scarcity
1
0
Fork 0
Code Issues 18 Pull requests Projects Releases Packages Wiki Activity Actions

Working on eval/apply. Unfinished, does not build. More significantly,

Browse source 
as the focus ot this prototype is supposed to be building things in
Lisp,
I've started deliberately copying stuff that mostly works directly from
the 0.0.6 branch into this branch. After all, if it's going to be
replaced in Lisp, it doesn't have to be the most elegant C.
This commit is contained in:
Simon Brooke 2026-04-25 21:52:05 +01:00
parent 63906fe817
commit f7eabb9b62
10 changed files with 1730 additions and 134 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/State-of-play.md
View file

@ -62,6 +62,26 @@ So I think I'm going to put up with the uncollected garbage until we get to that
However, any new C code (and there is going to have to be some) *must* be written in the sanitary but bureaucratic pattern.
#### 21:24
Well, at the end of the day I think the git log says it all:
```
commit 63906fe817d509adb6171a72d16c045c2793ebed (HEAD -> feature/reengineering-17-21)
Author: Simon Brooke <simon@journeyman.cc>
Date: Fri Apr 24 21:20:23 2026 +0100
Print is less badly broken. Read is less badly broken. GC is too aggressive.
commit 22b0160a266999c939c9a21df150542f8b2f0b25 (origin/feature/reengineering-17-21)
Author: Simon Brooke <simon@journeyman.cc>
Date: Fri Apr 24 09:22:06 2026 +0100
Builds and runs, but print is badly broken. Need some rethink.
```
I could just disable the garbage collector until I've got `eval`/`apply` working. I *believe* that with `eval`/`apply` I'll be able to automate all the garbage collection bookkeeping work. I hope so. Mark and sweep, or even my preferred mark but don't sweep, on a massively parallel machine, just doesn't bear thinking on.
## 20260421