about summary refs log tree commit diff
path: root/README.txt
diff options
context:
space:
mode:
authorIrene Knapp <ireneista@irenes.space>2026-10-05 19:54:39 -0700
committerIrene Knapp <ireneista@irenes.space>2026-10-05 19:54:39 -0700
commit39304d51c4a6d057e6515a9f75db2086940f6877 (patch)
treee7ed75c42d3a0bd877303e10cce9f7f9bd5d79fd /README.txt
parentb8798f26ee09c4b30ffe033bd657a7f4c99210e5 (diff)
move to a struct-based definition of compilation inputs
the migration process was a pain - order of operations for the rebuild was rough to figure out - but the actual implementation is way easier than all that stack juggling

Force-Push: yes
Change-Id: I8bbe4dfb39e5f0ed69f9759e87ac6ab79ec7558b
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.txt b/README.txt
index ff3e8fa..be65a21 100644
--- a/README.txt
+++ b/README.txt
@@ -305,7 +305,7 @@ built-in library.
 the compiler. When you have a change you want to try it out, you can use your
 existing copy of Evocation to compile a new one, like this:
 
-  $ echo 's" evoke.e" enchant' | ./evoke > evoke2
+  $ echo 's" evoke.e" include drop enchant' | ./evoke > evoke2
   $ chmod 755 evoke2
 
   You can then run ./evoke2 and try out the new features you added. Fun,
@@ -384,7 +384,7 @@ can be metacircular while you're metacircular.)
 also works on Forth programs, including Evocation itself. To produce the
 hex-dump version of Evocation, do:
 
-  $ echo 's" evoke.e" inscribe' | ./evoke > evoke.hex
+  $ echo 's" evoke.e" include drop inscribe' | ./evoke > evoke.hex
 
   It should run to completion, producing output in evoke.hex. Passing
 evoke.hex through ./hex will give a binary that's byte-for-byte identical to