Marius Ackerman

gocc3 included two major changes: 1. It supported an EBNF for input and 2. It supported David Pager's "Practical General Method" for generating LR(1) parsers as an option to the...

Hi Robin, The errors you got when you ran gocc on its own BNF were for the lexical elements which are not declared the grammar. gocc2 still uses a hand...

Oh and Robin, I assume you will fix the lexer backtracking as part of such project:)

@shivansh put his finger on one of the aspects of gocc that didn't receive sufficient attention originally. If I remember correctly I tried to implement error recovery according to the...

The reason for this error is that the gocc2 symbol table is not sophisticated enough to distinguish between an explicitly declared symbol (e.g. foo : ...) and and implicitly declared...

@awalterschulze @suntong It appears that you have created loops in your grammar. I commented out all the productions that were causing unused warnings and now gocc completes: > time gocc...

I like the idea but it seems to me that by wrapping the standard parser with the suggest parser the original semantics of parsing a complete sentence that ends with...

Since the suggest parser is not a proper stream parser I would also suggest calling it "suggest parser" rather than "stream parser". We might want to consider a proper stream...

Sorry guys. I was very busy this week and next week will be no better. @awalterschulze @mewmew: Do we go ahead with a separate parser constructor method?

Sorry this took so long -- I have been very busy. Gocc's current error reporting is unfortunately designed for syntactic errors with semantic errors as an add on. The error...