From 244072db39c1f6fa743fec38463f550f1b9608c4 Mon Sep 17 00:00:00 2001 From: Irene Knapp Date: Thu, 24 Sep 2026 17:26:07 -0700 Subject: "include" works under the hex transform now this means all the build invocations are now as simple as they can be without new abstractions of some sort, such as letting evoke take command-line parameters. yay! Force-Push: yes Change-Id: Id877159f995662b8d226a9ad937ed73228a9af05 --- README.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'README.txt') diff --git a/README.txt b/README.txt index a767f43..55ba61b 100644 --- a/README.txt +++ b/README.txt @@ -264,7 +264,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 labels.e elf.e transform.e execution.e evoke.e | ./evoke > evoke2 + $ cat evoke.e | ./evoke > evoke2 $ chmod 755 evoke2 You can then run ./evoke2 and try out the new features you added. Fun, @@ -332,18 +332,18 @@ can be metacircular while you're metacircular.) If you need to compile "hex", you can do so as follows: - $ cat labels.e elf.e hex.e | ./evoke > hex + $ cat hex.e | ./evoke > hex $ chmod 755 hex To produce the hex-dump version of it, do: - $ cat labels.e elf.e transform.e inscribe-hex.e | ./evoke > hex.hex + $ cat inscribe-hex.e | ./evoke > hex.hex The program "hex" is written in Evocation-assembly, but the hex transform also works on Forth programs, including Evocation itself. To produce the hex-dump version of Evocation, do: - $ cat labels.e elf.e transform.e inscribe-evoke.e | ./evoke > evoke.hex + $ cat inscribe-evoke.e | ./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