From 7acba568178af4048135a858a7ca9c6fb9c00520 Mon Sep 17 00:00:00 2001 From: Irene Knapp Date: Sat, 26 Sep 2026 18:27:44 -0700 Subject: refactor the compilation harness it's more declarative now. however, at the moment it only produces the one type of executable, so it's only for building "evoke", not "hex". hopefully that can be fixed soon. Change-Id: Id970b9952fcd73ba6da4fa503ae2f784afe1b8a7 Force-Push: yes --- README.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.txt') diff --git a/README.txt b/README.txt index e77c57f..ff3e8fa 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: - $ cat evoke.e | ./evoke > evoke2 + $ echo 's" evoke.e" 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: - $ cat inscribe-evoke.e | ./evoke > evoke.hex + $ echo 's" evoke.e" 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 -- cgit 1.4.1