The update of antlr from 3.2-11 to 3.5.2 introduces the issue.
antlr behaves differently and does not produce the same code.

Reply via email to