The idea of symlinking README.md to docs/Home.md didn't work for autogeneration.
For the `master` branch I'm going back to having a separate README.md. Thought should be given into making that update from docs/Home.md from time to time, but URLs need to be fixed up which is awkward.
This commit is contained in:
parent
b8bb923560
commit
0a22222042
3 changed files with 223 additions and 3 deletions
|
|
@ -1,6 +1,6 @@
|
|||
# Post Scarcity Software Environment: general documentation
|
||||
|
||||
Work towards the implementation of a software system like that described in [Post Scarcity Software](https://www.journeyman.cc/blog/posts-output/2006-02-20-postscarcity-software/).
|
||||
Work towards the implementation of a software system for the hardware of the deep future.
|
||||
|
||||
## Note on canonicity
|
||||
|
||||
|
|
@ -172,7 +172,7 @@ The following functions are provided as of release 0.0.6:
|
|||
| subtract | FUNC | `(- a b)`: Subtracts `b` from `a` and returns the result. Expects both arguments to be numbers. |
|
||||
| throw | FUNC | `(throw message cause)`: Throw an exception with this `message`, and, if specified, this `cause` (which is expected to be an exception but need not be).|
|
||||
| time | FUNC | `(time arg)`: Return a time object. If an `arg` is supplied, it should be an integer which will be interpreted as a number of microseconds since the big bang, which is assumed to have happened 441,806,400,000,000,000 seconds before the UNIX epoch. |
|
||||
| try | SPFM | `(try forms... (catch catch-forms...))`: Evaluate `forms` sequentially, and return the value of the last. If an exception is thrown in any, evaluate `catch-forms` sequentially in an environment in which `*exception*` is bound to that exception, and return the value of the last of these. |
|
||||
| try | SPFM | `(try forms... (catch symbol forms...))`: Doesn't work yet! |
|
||||
| type | FUNC | `(type object)`: returns the type of the specified `object`. Currently (0.0.6) the type is returned as a four character string; this may change. |
|
||||
| λ | SPFM | `(lamda arg-list forms...)`: Construct an interpretable λ function. |
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,36 @@
|
|||
# State of Play
|
||||
|
||||
## 20260326
|
||||
|
||||
Most of the memory architecture of the new prototype is now roughed out, but
|
||||
in C, not in a more modern language. It doesn't compile yet.
|
||||
|
||||
My C is getting better... but it needed to!
|
||||
|
||||
## 20260323
|
||||
|
||||
I started an investigastion of the [Zig language](https://ziglang.org/) and
|
||||
come away frustrated. It's definitely an interesting language, and *I think*
|
||||
one capable of doing what I want. But in trying to learn, I checked out
|
||||
someone else's [Lisp interpreter in Zig](https://github.com/cryptocode/bio).
|
||||
The last commit to this project is six months ago, so fairly current; project
|
||||
documentation is polished, implying the project is well advanced and by someone
|
||||
competent.
|
||||
|
||||
It won't build.
|
||||
|
||||
It won't build because there are breaking changes to the build system in the
|
||||
current version of Zig, and, according to helpful people on the Zig language
|
||||
Discord, breaking changes in Zig versions are quite frequent.
|
||||
|
||||
Post-scarcity is a project which procedes slowly, and is very large indeed. I
|
||||
will certainly not complete it before I die.
|
||||
|
||||
I don't feel unstable tools are a good choice.
|
||||
|
||||
I have, however, done more thinking about [Paged space objects], and think I
|
||||
now have a buildable specification.
|
||||
|
||||
## 20260319
|
||||
|
||||
Right, the `member?` bug [is fixed](https://git.journeyman.cc/simon/post-scarcity/issues/11).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue