diff options
Diffstat (limited to 'README.txt')
| -rw-r--r-- | README.txt | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/README.txt b/README.txt index 34cdb5a..a767f43 100644 --- a/README.txt +++ b/README.txt @@ -27,10 +27,10 @@ compiled Forths in that it targets a 64-bit architecture. In addition to being self-hosting, Evocation is also self-bootstrapping, meaning that the compiler can run in a special "show your work" mode which, instead of a regular binary, outputs a commented hex dump which is heavily -instrumented with explanations of the provenance of every single byte of ouput -and how to audit that it is correct. This hex dump is suitable for checking -into source control, and can then be converted to a binary executable through -a process that is itself straightfoward to audit. +instrumented with explanations of the provenance of every single byte of +output and how to audit that it is correct. This hex dump is suitable for +checking into source control, and can then be converted to a binary executable +through a process that is itself straightforward to audit. This hex-dump strategy rests on the insight, from the mescc and guix developers, that the difference between source code and binary is comments. @@ -233,10 +233,10 @@ compiler works; that stuff is in execution-suport.e. So, there's all those relatively normal compiler internals in those various files, which are all fairly self-contained... and then there's the -transformation facility. This is Evocation's most unique archictural decision, -and it's in transform.e. It's well documented, but it's also extremely -conceptually dense. Feel free to give it a skim, that's the only way to build -familiarity with these things, but you should probably have a solid +transformation facility. This is Evocation's most unique architectural +decision, and it's in transform.e. It's well documented, but it's also +extremely conceptually dense. Feel free to give it a skim, that's the only way +to build familiarity with these things, but you should probably have a solid understanding of the rest of the internals before you place any high expectations on yourself around understanding the transformation facility. @@ -309,7 +309,7 @@ Evocation's transformation facility in transform.e. The hex transform has the task of transforming an entire compilation process, which would otherwise produce an executable binary, and instead output a commented hex dump of that binary which describes its internals and their purpose, byte by byte, in -sufficient detail to allow a human reader to audit their correctnes. It will +sufficient detail to allow a human reader to audit their correctness. It will do this by passing through comments and call-stack information from the compilation process to the resulting output. |