New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] %apiprivate and %cup2 switches are incompatible [sf#124] #125

Closed
lsf37 opened this Issue Feb 15, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@lsf37
Member

lsf37 commented Feb 15, 2015

Reported by mranderson2010 on 2013-03-23 01:29 UTC
Jflex-1.4.3 with the cup2 patch applied generates bad code when combining the apiprivate switch and the cup2 switch.

A cup2 scanner implements the interface edu.tum.cup2.scanner.Scanner that contains the signature

> public ScannerToken<? extends Object> readNextTerminal()
> throws java.io.IOException;

The method is implemented in the generated scanner class, but the apiprivate switch changes the public modifier to private, leading to the error message
> cannot implement readNextTerminal() in edu.tum.cup2.scanner.Scanner; attempting to assign weaker access privileges; was public

@lsf37 lsf37 changed the title from %apiprivate and %cup2 switches are incompatible to [Bug] %apiprivate and %cup2 switches are incompatible [sf#124] Feb 15, 2015

@lsf37 lsf37 added this to the jflex bug milestone Feb 15, 2015

@lsf37 lsf37 added the bug label Feb 15, 2015

@lsf37 lsf37 removed this from the jflex bug milestone Feb 15, 2015

@lsf37 lsf37 added this to the 1.6.1 milestone Mar 1, 2015

@lsf37 lsf37 self-assigned this Mar 1, 2015

@lsf37 lsf37 closed this in 2d8fef4 Mar 1, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment