diff options
author | Colin Okay <cbeok@protonmail.com> | 2020-05-13 09:11:27 -0500 |
---|---|---|
committer | Colin Okay <cbeok@protonmail.com> | 2020-05-13 09:11:27 -0500 |
commit | 148c1728d09c94175ebbc3ce5827967985c9a2ac (patch) | |
tree | d2d56d4499462f0fa44fa36c40940e4a2b747c60 | |
parent | fbeb2bf8ba4e3c6452d80361c2cb7a1723c00013 (diff) |
some typos and typographical reconsiderations
-rw-r--r-- | examples/Tutorial.org | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/examples/Tutorial.org b/examples/Tutorial.org index 606fa63..730891a 100644 --- a/examples/Tutorial.org +++ b/examples/Tutorial.org @@ -237,10 +237,10 @@ T #<REPLAY-STREAMS:STATIC-TEXT-REPLAY-STREAM {1008A071C3}> #+END_SRC -The parser =(<<string "hey")= accepted exactly the string "hey" from -the input "hey dude" and resulted in the string "hey". +The parser =(<<string "hey")= accepted exactly the string =hey= from +the input =hey dude= and resulted in the string =hey=. -Notice that if you try to accept the string "dude" from the same +Notice that if you try to accept the string =dude= from the same initial input, the parse will fail: #+BEGIN_SRC lisp @@ -251,7 +251,7 @@ NIL #+END_SRC The parse resulted in failure (indicated by a second return value of -=NIL=) because, though "dude" appeared in the input, it was not at +=NIL=) because, though /dude/ appeared in the input, it was not at the beginning of the stream. At this point it seems clear that you will will want to define parsers @@ -264,9 +264,9 @@ that look something like this: #+END_SRC However, while each of the above will accept the right inputs, they -all result in strings, which probably isn't what you want. That is -"true" should probably result in =T=, "false" in =NIL=, and -"null" in.. hmm that's a tough one: perhaps a keyword called =:NULL=. +all result in strings, which probably isn't what you want. That is, +=true= should probably result in =T=, =false= in =NIL=, and +=null= in.. hmm that's a tough one: perhaps a keyword called =:NULL=. This is where =<<map= comes in. @@ -340,7 +340,7 @@ a literal value upon success. ** The Fundamental <<bind, Parsing Numbers - Luckily, =parzival= includes to parsers that will get you most of + Luckily, =parzival= includes two parsers that will get you most of the way to parsing JSON numbers. They are =<int<= and =<real<=, which parse integers and floating point numbers respectively. What =<real<= does not do, however, is parse exponential components of |