log4b0at

your `UnexpectedThing` rule cannot handle keywords, expressions or others atoms of your grammar, it just return a single character: `text().substring(0,1)`, so what you do is exactly the same thing that...

@Mingun What you say is wrong, you can override my implicit "unexpected rule" by adding an "UnexpectedThing" in the concerned rule, as you said yourself. An implicit rule is fully...

It is a solution certainly, but too little accessible and difficult to maintain. Anyway thank you for your code, it's always good to take. I agree that the direct implementation...

@futagoza Surely

I dont understand well the problem that you trying to raise, can you give me more examples about ?

``` defect: bug microphone: bug disease: bug hobbyist: bug ``` "What should the error messages there be?" You get that with actual error handling: > Line 1, column 1: Expected...

if you want try yourself, I quickly made a code for 0.10 version of pegjs, replace (in your parser) `peg$buildStructuredError` by ```javascript function peg$buildStructuredError(expected, found, location) { if (typeof peg$parseunexpected...

Use a tokenizer has a cost. such feature is simple to implement and cost nothing to nobody

Hello, I just made a pull request for this functionality, following your advices, namely the use of the error function, much more consistent than a return, suggested by @norech. And...