evocation - Call forth the blue-green flame of computation from the universe, weave its energies into a fabric, that we may share our blood with it.

Age	Commit message (Collapse)	Author
2026-05-17	implement log-load-create; add all the pack/unpack stuff to core.e	Irene Knapp
	Force-Push: yes Change-Id: I04dd65a9eec71f9b50c8875bdcbe5d4be59888d5
2026-05-16	the skeleton of the log-load transform is in place now	Irene Knapp
	it doesn't actually output anything, but it all runs without crashing Force-Push: yes Change-Id: I48f2e647044df0ae3db961c747cee31a8826ecf3
2026-05-16	ah, oops, there was a bug in the label transform for compiled words	Irene Knapp
	fixed now also a bunch of small things towards adding a log-load transform Force-Push: yes Change-Id: I6eeb94d896a7e79092886d7b60e9404c31b2ba6f
2026-05-16	it's much closer, most of the labels work correctly now	Irene Knapp
	Force-Push: yes Change-Id: I45662e60c0035758a2cd57d971031eb0562eccb7
2026-05-15	make the label transformation work all the way, no crashing	Irene Knapp
	the code doesn't quite run yet, that'll be a future CL Force-Push: yes Change-Id: I71e6a45127c1fc37906d902e36142c17afef2a21
2026-05-15	document the assumptions between labels and transforms	Irene Knapp
	also some minor cleanup that ie. fixes alignment padding Force-Push: yes Change-Id: Ia8fcb9a44e05e37751cc1b8334aa72add7e62353
2026-05-15	transform runs inside the label loop now, and is able to do compilation	Irene Knapp
	wow! yes. good. now it needs to actually generate label calls :) Force-Push: yes Change-Id: Ide4336e00aa6860fe55c956063303edc873c6d9b
2026-05-15	fix things up so it gets through cold-start	Irene Knapp
	then it crashes on warm-start because warm-start doesn't exist yet Force-Push: yes Change-Id: I9eba481b31d48f9d32c3790f296204c5c8d90938
2026-05-11	implement all the core Forth stuff in Evocation-assembly	Irene Knapp
	also, add support for ;asm and stuff Force-Push: yes Change-Id: I904bc0c31e7e4c8b0abc7790f3af5d20c275f2a5
2026-05-09	implement more stuff in interpret.e	Irene Knapp
	it depended on the execution-model stuff, for the "next" macro. in general, any word implemented in assembly will depend on that. so, the execution stuff is moved into its own file, leaving evoke.e with only the job of bringing everything together. that's a little disappointing because talking about the execution model seems like a good introduction to the whole topic, but perhaps the problem can be solved down the line with literate programming... Force-Push: yes Change-Id: Ic2fe22dcc39980ef75763ae293e41024abc8ba38
2026-05-09	a minor documentation error in the word header format	Irene Knapp
	oops - the last CL was supposed to fix this, but it was inadvertently left out Force-Push: yes Change-Id: I4edf5abed315bea51abcd98ad67cd28782a62efe
2026-05-08	add a rough draft of a self-hosted evoke	Irene Knapp
	Force-Push: yes Change-Id: Icf69cdfe7cf31fda07031bbc848c3ce2acb8cca1