grammarinator-generate fails for the PostgreSQL grammar

[renatahodovan]

grammarinator-generate fails for the PostgreSQL grammar

[renatahodovan]

Hi @mrigger !

While Grammarinator and ANTLR share many design patterns, like the possibility of inlined code and the definition of superclasses, they cannot share the same inlined code or the same superclass. It's true simply because their purposes are different: recognition vs. generation. Furthermore, while ANTLR supports inlined code in multiple languages, Grammarinator only supports Python right now.

Regarding the failures in this report, the first two errors are caused by inlined Java parser code in the grammars. On one hand, their purpose is to improve parsing, hence they are useless in our generation scenario. On the other hand, they are written in Java which is not supported by Grammarinator. To avoid these kind of issues, please use the --no-actions CLI option with grammarinator-process. (If you need, you can use inline code ofc, but only in Python.)

The third error is due to the "missing" PostgreSQLParserBase superclass, which is required by the generated ANTLR parser, but not needed by the generated fuzzer (recognition vs. generation again). To overcome this issue, you should comment out the superClass = ... options from the raw grammars. (If you need your own superclass, then you can use this syntax to define it ofc, but you must ensure to place the superclass file on PYTHONPATH.)

I hope it helps! Please let me know if you have any further questions.

Cheers,
Reni

[renatahodovan]

@mrigger I think we can consider this issue as "fixed". Please feel free to reopen if it still stands.

[mrigger]

Thanks a lot for the detailed explanation!