aboutsummaryrefslogtreecommitdiff
path: root/content/blog
diff options
context:
space:
mode:
authorJulien Dessaux2021-10-02 00:15:05 +0200
committerJulien Dessaux2021-10-02 00:15:05 +0200
commit1199b2a0639cc533adc98ab01af244f0830cd106 (patch)
tree6b90dc00953d8e959a1bb0e9e058f6b7ed87980b /content/blog
parentWrote never split the difference book article (diff)
downloadwww-1199b2a0639cc533adc98ab01af244f0830cd106.tar.gz
www-1199b2a0639cc533adc98ab01af244f0830cd106.tar.bz2
www-1199b2a0639cc533adc98ab01af244f0830cd106.zip
Fixed mistake in gofunge98 blog article
Diffstat (limited to 'content/blog')
-rw-r--r--content/blog/golang/funge98-interpreter.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/golang/funge98-interpreter.md b/content/blog/golang/funge98-interpreter.md
index 7adea71..0228b58 100644
--- a/content/blog/golang/funge98-interpreter.md
+++ b/content/blog/golang/funge98-interpreter.md
@@ -18,7 +18,7 @@ The space character is special in the sense that the funge space is supposed inf
Resizing the funge space means reallocating things in order to properly handle the wrapping of the instruction pointer, which is one a the most fun things in Funge-98! This instruction pointer that can travel in any direction on the grid space? It can really travel in any directions, left right up down but also diagonals or any vector really. And if the instruction pointer would leave the grid because of its travel it wraps around. Wrapping aound is intuitive when talking about cardinal directions, but not so much for an arbitrary vector.
-I was also trapped by the line feed character handling, which is only used in Trifunge to process the z coordinate. The spec was not clear but in order to pass the mycology test suite you need to ignore this character if found in the input file, much like you would handle a carriage return in Onefunge.
+I was also trapped by the form feed character handling, which is only used in Trifunge to process the z coordinate. The spec was not clear but in order to pass the mycology test suite you need to ignore this character if found in the input file, much like you would handle a carriage return in Onefunge.
## Conclusion