From 174f4686444f13b1e944af807864dc8c8133bd44 Mon Sep 17 00:00:00 2001
From: Colin Okay <cbeok@protonmail.com>
Date: Thu, 24 Sep 2020 16:31:05 -0500
Subject: addded note about gotchas using <<or

---
 parzival.lisp | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/parzival.lisp b/parzival.lisp
index 71bb6c0..9f80fef 100644
--- a/parzival.lisp
+++ b/parzival.lisp
@@ -182,7 +182,12 @@ CONDITION is true, then the THEN parser is run, otherwise the ELSE parser is run
 
 (defun <<or (&rest parsers)
   "Tries each parser one after the other, rewinding the input stream after each
-   failure, and resulting in the first successful parse."
+   failure, and resulting in the first successful parse.
+
+   Hence, the order in which the parsers appear is significant. As a
+   general rule, you should list the most specific parsers first.
+
+   E.g. (<<string \"foobar\") is more specific than (<<string \"foo\")"
   (cond ((null parsers) <fail<)
         ((null (cdr parsers)) (car parsers))
         (t
-- 
cgit v1.2.3