Awesome! You impress me with your speed here. Please include at least a one-liner in the README explaining how to have 'Johns method' of error reporting be the one in use, so users can swap it in and see if it works better for them.
I think a lot of users are not going to have the skill/time to write their own custom error reporting methods; those who do (like John) should be encouraged to share them publicly, and ideally Parslet docs will advertise their availabiltiy (whether they're included in Parslet source like John's example at the moment, or included in other gems, no problem either way). On 5/15/2012 10:56 AM, Kaspar Schiess wrote: > Self quotation ahead: > >> * Make the system pluggable, implement 'Johns method' of error reporting >> as a demonstration. > DONE. > >> * Make the default parse be a two-phase parse: Once without generating >> errors, once with errors IF we fail. (see below) > DONE. Improves the speed of the engine in the success case. > >> * This is the distant future, but perhaps: Introduce other methods for >> error reporting? Ideas, anyone? > The discussion here: https://github.com/kschiess/parslet/issues/64 > should be illuminating to everyone aiming for such an error reporter. > > Changes are on master and will be released as soon as I can close #64 > with good conscience. > > regards! > kaspar > >
