New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reintroduce error recovery from pb1 #42

Open
sirthias opened this Issue Dec 20, 2013 · 6 comments

Comments

Projects
None yet
7 participants
@sirthias
Owner

sirthias commented Dec 20, 2013

Can be implemented largely by simply wrapping a parser and using a special ParserInput, which allows for insertion and removal of virtual characters in the same way as the MutableInputBuffer from pb1.

The techniques used for recovery in pb1 should still work much the same as before.

@edko99

This comment has been minimized.

edko99 commented Feb 20, 2015

I am using parboiled2 to build a parser for a small language, and I really like its speed and flexibility. Having error recovery would really help in building a user-friendly text editor for my language. If this feature will not be built, is there any good blog post that explains in detail the techniques used by parboiled1?

@machaval

This comment has been minimized.

machaval commented Mar 6, 2015

It will really help us to start building tooling around a language be are creating.

@PoloShock

This comment has been minimized.

PoloShock commented Mar 28, 2015

I'm currently developing an IDE-like environment with syntax error hints for my users. For now I use parboiled1 but it is very slow for some inputs so I'm considering switching to parboiled2. It would be no-brainer if it had error recovery as the parboiled1 has.

@ppopoff

This comment has been minimized.

ppopoff commented Nov 16, 2015

+1 for this feature

@JuPfu

This comment has been minimized.

JuPfu commented Nov 16, 2015

Would be great to have this feature in parboiled2!

@ozgunduz

This comment has been minimized.

ozgunduz commented Jul 27, 2017

+1 for this feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment