evocation/core.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-09-21T04:41:07+00:00fresh line for alignment padding comments2026-09-21T04:41:07+00:00Irene Knappireneista@irenes.space2026-09-21T04:41:07+00:00urn:sha1:f7a320e19422bef7021bf03b3362b6c6c05c548f
this fixes the thing where, if alignment padding was zero-length, the comment could wind up on the same line as the preceding thingy, causing confusion
Force-Push: yes
Change-Id: Ie7490370bf66a2f9b82df584236320bd88338e39
make the magic-comment tab stops function like real tab stops2026-09-21T04:22:12+00:00Irene Knappireneista@irenes.space2026-09-20T21:02:31+00:00urn:sha1:3275f7932b3f109d798b9303b1e3bfc052a48d4d
fun! fiddly! :D
fixing one-off column alignment issues is like stimming for coders
(which is to say, like stimming)
Change-Id: I1037ec27b863f90117fb22a29ef52d0ba460c7d5
Force-Push: yes
add a special word for magic-comment tab stops2026-09-20T18:16:45+00:00Irene Knappireneista@irenes.space2026-09-20T18:16:45+00:00urn:sha1:170f925a23e0c54a97dde4c8294898549424d332
Force-Push: yes
Change-Id: I7ba182f5939aa3b5d280fb48673e2cc74d72e8ea
magic comments work in the log-load transform now2026-09-20T07:51:52+00:00Irene Knappireneista@irenes.space2026-09-20T07:51:52+00:00urn:sha1:4370f257141fee85adf0a2a3e76b7881cb1b8e7a
that was pleasingly straightforward
Force-Push: yes
Change-Id: I92b66fbb37ed5df3ef3f733e8679747a9a232373
magic comments for a bunch more small stuff2026-09-18T22:12:50+00:00Irene Knappireneista@irenes.space2026-09-18T22:12:50+00:00urn:sha1:31509055e11946ecc118ebbc6f72e458b17de918
especially in the label-transform output
there's more to do, but there are additional magic-comment features that would be handy, so we're checking this in now so that those can be cleanly kept in their own CL
Force-Push: yes
Change-Id: I97a67caddc3f3150c349b7956c1d715db909d1a9
redo the hex dump comments for alignment to use the regular magic commands2026-09-16T01:00:31+00:00Irene Knappireneista@irenes.space2026-09-16T01:00:31+00:00urn:sha1:e1f5c4e72830cc9ce900e1884d3338f1c82060fd
previously, alignment had been a special-cased type of metadata entry, with a special trap on packalign. now it uses the same programmable setup everything else does. much simpler, and prettier output.
this CL also contains some modest reformatting of section headers in the hex dump
Force-Push: yes
Change-Id: I21554e92f6af6ddefa937dad8073b89657f85d64
do magic comments from the label transform when inside the hex transform2026-09-15T22:23:51+00:00Irene Knappireneista@irenes.space2026-09-15T21:14:50+00:00urn:sha1:4137177c016928a6d255bbef762f0d220945083c
the meaning of them in that setting is a bit different, which deserves to be documented eventually
Change-Id: Ia7725bc776420c0ad62091a2e5100700868a6bfa
Force-Push: yes
comments: document trap methodology; rename parameters to packalign2026-09-03T23:41:29+00:00Irene Knappireneista@irenes.space2026-09-03T23:41:29+00:00urn:sha1:2ae673e2ec8aab2baf61d0fb63e41967383f7d3a
"alignment byte count" was confusing since it could mean either the input value that should be used as the modulus base for the desired byte offset, or the number of bytes actually needed to attain modulus zero under that base. in "packalign" itself, this wasn't too confusing, but the hex transform's trap of packalign needs to work with both values alongside each other, so the name needed to be clearer. it is renamed to "alignment byte width".
of course, Evocation doesn't have parameter names as-such, this is just a comment thing
Force-Push: yes
Change-Id: I1c227200ce0b2f6a852c1dc2f2c73f8cdf474f7a
change the transforms to take their end delimiters as parameters2026-08-29T03:12:35+00:00Irene Knappireneista@irenes.space2026-08-28T12:28:35+00:00urn:sha1:6e0227328154e18810d8dfa4489bf84c9c15cbf7
this will not be useful until read-to-buffer also does, but it's a step towards that
Force-Push: yes
Change-Id: Icf03088c9e52e427a5c130949e9ba85655d59044
make a decision on where to keep find-in and document it2026-05-29T04:49:05+00:00Irene Knappireneista@irenes.space2026-05-29T04:49:05+00:00urn:sha1:e13473675c30ddfbacd42a716f166026b37402fb
Force-Push: yes
Change-Id: I5e8d8ae4a6e07c2dfa38abc7b19a962932a210bf