Martin von Loewis wrote:
Yes, but why not YACC? Is Antlr so much better, or is
I think the advantage that Barry saw is that ANTLR generates Java in addition to C, so it could be used in JPython as well. In addition, ANTLR is more advanced than YACC; it specifically supports full EBNF as input, and has better mechanisms for conflict resolution.
Oh, OK. Thanks.
Personally, I'm quite in favour of having the full parser source (including parser generator if necessary) in the Python source distribution. As a GCC contributor, I know what pain it is for users that GCC requires bison to build - even though it is only required for CVS builds, as distributions come with the generated files.
I see your point, but the practical solution that we can do today is to use YACC, bison, and distribute the generated parser files.