evocation/log-load.e, branch v3.0Call 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=v3.02026-05-29T03:28:48+00:00change the parameter order for memcopy and memmove2026-05-29T03:28:48+00:00Irene Knappireneista@irenes.space2026-05-29T02:34:07+00:00urn:sha1:3b00a5376036bb3f50a1a1f97d136305a2d03a57
that was surprisingly involved, but it feels like the right thing to do
Change-Id: Ia2f38c7278f4237cebd0435d27131fe32dbc3718
Force-Push: yes
fix our first binary reproducibility issue (wow)2026-05-23T03:04:58+00:00Irene Knappireneista@irenes.space2026-05-23T03:04:58+00:00urn:sha1:6a11bca93d6b6ac4d3e5a1b51c2b50ce0720d2a7
with this fix, the first-generation and second-generation builds are precisely identical
it was an unused codeword in the bootstrapped docol, under the label transform, which inadvertently had a value from the host address space. the fix required some creativity.
Force-Push: yes
Change-Id: I05b373b4231fa093454fa31891784de16d81bb18
small changes towards self-hosting2026-05-22T10:57:59+00:00Irene Knappireneista@irenes.space2026-05-22T10:57:59+00:00urn:sha1:3f3bda4692b4017c7ad6ed1c434313b9dcc62cfb
Force-Push: yes
Change-Id: I6cf15b4e37b66a04afd5af9dfd9cc3d5eb52b894
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
started cleaning up all the log-loaded functionality2026-05-21T23:52:41+00:00Irene Knappireneista@irenes.space2026-05-21T23:52:41+00:00urn:sha1:a7a670e41bdaf9c57bfe7bbd802158de91d7d94d
it's in dynamic.e for now
Force-Push: yes
Change-Id: I4d0c5917eccd58cb881850faee0728d786010c27
Add high-level flow control to the log-load transform2026-05-21T20:25:03+00:00Irene Knappireneista@irenes.space2026-05-21T17:55:33+00:00urn:sha1:09e1758b4380767647a238f88f51baa85e6e4df5
that was a lot
Change-Id: I6ae9c371fe1fe6fd2757d20df73a748339fa89d1
Force-Push: yes
some comment stuff, and implement "keyword"2026-05-21T09:43:35+00:00Irene Knappireneista@irenes.space2026-05-21T09:43:35+00:00urn:sha1:fe5ad105a8ca461eae368178706655753219ab92
Force-Push: yes
Change-Id: Iecf4079b9629f9c041b7fe994b1a69b6ef7b6dd0
okay, s" and ." work all-the-way in the log-load transform now2026-05-21T07:23:32+00:00Irene Knappireneista@irenes.space2026-05-21T07:23:32+00:00urn:sha1:189f0c0de22150f944e067b686b4cfe81af5fcb8
wow those were hard ones. it's very squirelly what happens when. hopefully these new and reorganized docs will make it easier to understand next time...
Force-Push: yes
Change-Id: I8f3b86900ca1794afc3e607c2180dd05ea168cc7
so yeah, docol, exit, and lit all work in log-load now2026-05-21T03:03:01+00:00Irene Knappireneista@irenes.space2026-05-21T02:59:18+00:00urn:sha1:2fcfc1bcb59e0c1716a6a7dffcad4e0b90790a20
also s" and ." work in the label transform, and are used to produce an important error message during the log-load routine, since we can't know whether log-loaded words exist until runtime
sweet, right?
Change-Id: I6a67139538c2cbcef40a1093202b2b4e0ad6febb
Force-Push: yes
colon, semicolon, and compiled integers all work with log-load now2026-05-21T01:23:07+00:00Irene Knappireneista@irenes.space2026-05-21T01:23:07+00:00urn:sha1:53f52a67b7c5bb8af12c92a2f3a219e75dd9b0c3
yay
next up is to figure out why calling newly-defined docol-based words with it does not work
Force-Push: yes
Change-Id: I9c5f50d20f43ad8a15b6db58e046f1e0bb158266