Giter Club home page Giter Club logo

Comments (4)

yhirose avatar yhirose commented on June 14, 2024

@LagMeester4000, thanks for the feedback. As you noticed, the parser unfortunately detects and reports only the very first error at this point. Sorry about that...

I actually researched about 'error handling/recovery in PEG' with some technical papers available on Internet, but I realized it wasn't easy task and I didn't have time to work it. I'll hopefully come back to this subject and try to find a reasonable way to implement it, so that this library could be more useful for users. Thanks for bringing up this matter!

from cpp-peglib.

LagMeester4000 avatar LagMeester4000 commented on June 14, 2024

Yes, I thought about it too, and it doesn't seem easy to implement on a generic parser like this, because finding the end of an expression could be wildly different for each grammar. Then again, I don't know that much about this stuff.

Thanks for the quick reply!

from cpp-peglib.

mqnc avatar mqnc commented on June 14, 2024

The way I'm dealing with it is by making a syntaxerror rule that accepts anything and prints a warning when discovered.

expression <- assignment / branch / loop / function / syntaxerror
syntaxerror <- (!\n .)* \n

The ordered priorization of PEG makes this very nice. Only if it's none of the known things, it must be a syntax error. The error consumes the line (or the character or whatever you should skip in an error case) and we can move on.

I am aware that this is by far not bullet proof. Consider this:

error <- .
number <- binary / decimal
binary <- [0-1] / error
decimal <- [0-9] / error

Now this is a stupid example since you could just fix it by swapping binary and decimal in the number rule. My point is: The danger of this approach is that you might throw an error from within a branch that you're not supposed to be in and not only will you get an incorrect warning, the parser will also continue in this false branch because everything matched since the error rule consumes anything.

So when you use this, you have to be sure "At this point, there is no way that I could be in another branch where this could be correct." And there are probably more pitfalls to consider. But so far it has served me well. With this I can write a giant file that I want the parser to be able to parse and then step by step create the grammar and the parser parses everything it already understands.

from cpp-peglib.

yhirose avatar yhirose commented on June 14, 2024

Close it for now.

from cpp-peglib.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.