commit 8a17ea5edf0da46db4e8c102f7b350a934d0cc98
parent 5868cfb8c3031948b2f60a88d7887c3c2d981920
Author: Luxferre <lux@ferre>
Date: Mon, 19 Sep 2022 18:22:08 +0300
typofix
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -241,7 +241,7 @@ While Equi definitely is a minimalist runtime, it's not limited to a 16- or 32-i
### Why is there a distinction between instructions and custom-defined words? Forth doesn't have one!
-This distinction only exists to simplify program interpretation flow. Forth uses whitespace as an essential syntactic feature to delimit words and literals, Equi does not. Therefore, the only way to distinguish between a string literal and compiled word definition is my the means of a special instruction. And using for the compiled words the same approach as for the hexadecimal short literals (automatically try to detect one before an instruction) would be too resource-heavy for the oldest systems as it would involve computing CRC16 on the literal stack contents every single instruction. A dedicated instruction that denotes what to do with the literal stack is much more convenient and straightforward to implement.
+This distinction only exists to simplify program interpretation flow. Forth uses whitespace as an essential syntactic feature to delimit words and literals, Equi does not. Therefore, the only way to distinguish between a string literal and compiled word definition is by the means of a special instruction. And using for the compiled words the same approach as for the hexadecimal short literals (automatically try to detect one before an instruction) would be too resource-heavy for the oldest systems as it would involve computing CRC16 on the literal stack contents every single instruction. A dedicated instruction that denotes what to do with the literal stack is much more convenient and straightforward to implement.
### Is Equi self-hosted, i.e. can it compile and run a new version of itself?
