Skip to content

Commit dcb44cc

Browse files
committed
remove stray curly, tweak readme txt
1 parent 97d9504 commit dcb44cc

File tree

2 files changed

+7
-8
lines changed

2 files changed

+7
-8
lines changed

readme/Changelog.scalatex

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
within a certain set.
2323

2424
@li
25-
Added @code{CharIn.raw}, @code{CharsWhile.raw}, @code{CharPred.raw}
25+
Added @code{CharsWhile.raw}, @code{CharPred.raw}
2626
intrinsics, which are identical to the non-@code{raw} versions except
2727
these do not pre-compute a lookup table for use during parsing. This
2828
could be useful if you find your parsers are taking too long to

readme/WritingParsers.scalatex

+6-7
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,12 @@
1818
You can also wrap the strings in an @hl.scala{IgnoreCase("...")} if you want the matching to be case-insensitive.
1919

2020
@p
21-
The @code{P(...)} lets you write mutually recursive parsers;
22-
without it you run into circular initialization problems and
23-
@code{NullPointerException}s. It also provides that parser with a
24-
nice, human-readable name that is derived from the @hl.scala{{val}
25-
it is being assigned to. In general, every time you assign a parser
26-
to a @hl.scala{val}, you should wrap it in @code{P(...)} to allow
27-
for recursion and assist your future debugging.
21+
The @code{P(...)} lets you write mutually recursive parsers, without
22+
running into circular initialization problems, and gives the parser a
23+
nice, human-readable name (from the @hl.scala{val}
24+
it is being assigned to) which appears in parse error messages.
25+
In general, every time you assign a parser
26+
to a @hl.scala{val}, you should wrap it in @code{P(...)}.
2827

2928
@sect{Sequence}
3029

0 commit comments

Comments
 (0)