diff options
author | Colin Okay <cbeok@protonmail.com> | 2020-04-24 17:00:43 -0500 |
---|---|---|
committer | Colin Okay <cbeok@protonmail.com> | 2020-04-24 17:00:43 -0500 |
commit | 47c2db531c0e18c25ef3d4261346de0294100cf5 (patch) | |
tree | 3d5bed569d3c4150ad9e2b41cff86a36b9ecb1ef | |
parent | 1588dd1df103299e4bad97a1c1d7b78c1a11e7df (diff) |
readme update
-rw-r--r-- | README.org | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -19,8 +19,8 @@ *completely optional* naming conventions that =parzival= adopts. 1. Names beginning and ending in a =<= are *parsers*. - 2. Names that begin with =<<= are *parser-combinators*, i.e. functions that - accept and return parsers. + 2. Names that begin with =<<= are *higher-order functions* that accept + or return parsers. #+begin_src lisp @@ -70,9 +70,9 @@ PARZIVAL-USER> T #+end_src -In the last example the string ="foozball"= is not a real, so the -parse fails, resultin in nil. You can examine the third return value -to see where in the input stream the parse failed. +In the last example the string ="foozball"= does not represent a real +number, and hence, the parse fails. You can examine the third return +value to see where in the input stream the parse failed. ** An Extended Silly Example @@ -117,7 +117,7 @@ PARZIVAL-NUMBERS> (ta-dah) -*** the code +*** The Code #+BEGIN_SRC lisp |