Bug#820086: More info

[olivier sallou]

Le mar. 5 avr. 2016 à 14:13, Emmanuel Bourg  a écrit :

> Le 5/04/2016 13:35, olivier sallou a écrit :
>
> > With op being optional it seems this version of antlr tries to bypass
> > the token. It behaves differently from previous releases.
>
> Hi Olivier,
>
> I suggest using the antlr3.2 package. Jython was affected by a
> regression with antlr 3.5 too and I uploaded the previous release as a
> separate package to address this issue.
>

I could patch the logol code to work with antlr 3.5, even if I do not
understand why it does not work nicely on optional token. I gonna push the
patch on logol anyway to try to keep pace with available packages, but I
keep in mind this 3.2 package in case other regressions where to be found
as fallback mechanism.

Thanks

Olivier


>
> Emmanuel Bourg
>
>
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#820086: More info

[Emmanuel Bourg]

Le 5/04/2016 13:35, olivier sallou a écrit :

> With op being optional it seems this version of antlr tries to bypass
> the token. It behaves differently from previous releases.

Hi Olivier,

I suggest using the antlr3.2 package. Jython was affected by a
regression with antlr 3.5 too and I uploaded the previous release as a
separate package to address this issue.

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#820086: More info

[olivier sallou]

After digging, issue seems related to optional tokens.

In my grammar I have:

op=(',' | ';'  | '|')? {  }

If I force op to be mandatory, and adap a little the rest of my grammar to
match, it works fine.
With op being optional it seems this version of antlr tries to bypass the
token. It behaves differently from previous releases.
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.