evocation/input.e, branch mainCall forth the blue-green flame of computation from the universe, weave its energies into a fabric, that we may share our blood with it.
http://code.irenes.space/evocation/atom?h=main2026-05-29T04:34:03+00:00swap the parameters to "entry-flags!"2026-05-29T04:34:03+00:00Irene Knappireneista@irenes.space2026-05-29T04:34:03+00:00urn:sha1:a00f83c9446159eaf9ac817dfae5291cb226ab7a
Force-Push: yes
Change-Id: I11f3eb1079d27a7306d6ed1e8e4b9fd6fb7d3a4a
add the ability to bind signal handlers2026-05-28T10:22:11+00:00Irene Knappireneista@irenes.space2026-05-27T02:41:59+00:00urn:sha1:d9a82e9f3c87aa318fb05819249656b43fde15e3
and a useful example one ;)
this also involved fixing the failure cases in input.e to handle EINTR correctly. it required a lot of tracing, but now the expected state of the stack is much better commented for next time.
many thanks to @cks@mastodon.social who found code in the Go compiler which had the details of what's required in regard to the restorer, which made the whole thing work, and to @snowfox@tech.lgbt who did some experimental testing around the exact requirements. both those contributions are reflected in the documentation added with this CL. additional thanks to everyone who chimed in on the fedi thread, your comments kept us going!
Force-Push: yes
Change-Id: I97fd89426bf807df5565e011d3665f7e904fa138
deal properly with EINTR from sys-read2026-05-27T07:07:38+00:00Irene Knappireneista@irenes.space2026-05-27T07:07:38+00:00urn:sha1:33fb92edc2a9958234b1bc2431a17fa4edbd83ea
this will be necessary to resume after running a signal handler. it had a bug where any error code other than ENOENT would be treated as a number of bytes read, resulting in a negative value for the buffer's logical length. amazingly this didn't crash, but it wasn't great.
anyway now that's all fixed
Force-Push: yes
Change-Id: I1c2b45d8efd531c121c5695cdf0cc74609c80547
de-branch'd all the internals2026-05-22T12:34:11+00:00Irene Knappireneista@irenes.space2026-05-22T12:32:50+00:00urn:sha1:02a165b1e5ce2960207976e0c27b568ab2d33f8d
so it's all just high-level flow control now, which makes it load in itself
the output isn't identical on the first self-compilation, but it converges on the second
with this, it is officially self-hosting. WOW.
Force-Push: yes
Change-Id: Ic14de1dae209b200cada269b07c3826c86fa494f
it runs!!!!!! it interactively reads input and everything2026-05-22T07:29:03+00:00Irene Knappireneista@irenes.space2026-05-22T07:29:03+00:00urn:sha1:ed702c3b88953112a3682c818a6e801549e1b461
only some of that actually works, but hey, it's a start
Force-Push: yes
Change-Id: Ib82beb695be1a18de8aaaf3040b7c632851c6002
the interpreter fully compiles now2026-05-22T06:38:32+00:00Irene Knappireneista@irenes.space2026-05-22T06:38:32+00:00urn:sha1:5ae0fdad3c7df2fc02acfc3b8f36d96c5d07bcd4
doesn't work quite yet. close :)
Force-Push: yes
Change-Id: I71b6e788790fe2ca8e07dae95e9ad6e39d0664c0
okay, input buffers should work now (untested though)2026-05-22T01:30:52+00:00Irene Knappireneista@irenes.space2026-05-22T01:30:52+00:00urn:sha1:5183b72b296b82a6a39f8412a3de2ac77be92c73
the word "variable" also needed special treatment, in the same way that "keyword" did. it's not immediately clear why.
Force-Push: yes
Change-Id: I15fae39b1b9ec928281150c76260940717b8e27a
dynamic.e is split up again, and more progress2026-05-22T00:57:18+00:00Irene Knappireneista@irenes.space2026-05-22T00:57:18+00:00urn:sha1:ff09b120141e9d8acbd930d44c3f0596eb05a016
see dynamic.e, input.e, interpret.e, and flow-control.e
there were a couple things in the log-load transform that need to work in compile mode, too
Force-Push: yes
Change-Id: I7caac3b9205f36f7e082a3fd280561d67e27942c