From ceebc8cda1a653465a7146e09abe2f8ac1addb8d Mon Sep 17 00:00:00 2001 From: Adrian Sampson Date: Sun, 31 Jan 2016 12:19:35 -0800 Subject: [PATCH] Better error position explanation Based on @Mingun's help. --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 47730ca..4f2ebea 100644 --- a/README.md +++ b/README.md @@ -458,9 +458,12 @@ character class that failed to match: > Expected [0-9] but "a" found. Aside from the text content of messages, human-readable names also have a -subtler effect on *where* errors are reported. PEG.js prefers shorter matches -for named rules and longer matches for unnamed rules. For example, for this -rule matching a comma-separated list of integers: +subtler effect on *where* errors are reported. PEG.js prefers to match +named rules completely or not at all, but not partially. Unnamed rules, +on the other hand, can produce an error in the middle of their +subexpressions. + +For example, for this rule matching a comma-separated list of integers: seq = integer ("," integer)*