Skip to content
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] single-line %initthrow option fails [sf#50] #52

Closed
lsf37 opened this issue Feb 15, 2015 · 4 comments
Closed

[Bug] single-line %initthrow option fails [sf#50] #52

lsf37 opened this issue Feb 15, 2015 · 4 comments
Labels
bug

Comments

@lsf37
Copy link
Member

@lsf37 lsf37 commented Feb 15, 2015

*Reported by anonymous on 2002-01-29 03:12 UTC
The syntax

%initthrow{
IOException, Error
%initthrow}

works fine, but

%initthrow IOException, Error

does not, despite the documentation (in 1.3.5)

@lsf37 lsf37 changed the title single-line %initthrow option fails [Bug] single-line %initthrow option fails [sf#50] Feb 15, 2015
@lsf37 lsf37 added this to the jflex bug milestone Feb 15, 2015
@lsf37 lsf37 closed this Feb 15, 2015
@lsf37
Copy link
Member Author

@lsf37 lsf37 commented Feb 15, 2015

Commented by lsf37 on 2002-01-30 09:03 UTC
Logged In: YES
user_id=93534

I could reproduce the error to a degree:
%initthrow (and the other %throw directives, too) do not
work when there's an extra space after the exception list.
Otherwise they should work as specified.

So the workaround is: make sure that the last "r" of Error
is really the last character in the line.

I'll fix the extra-space thing in the next release, of course.

@lsf37
Copy link
Member Author

@lsf37 lsf37 commented Feb 15, 2015

Updated by lsf37 on 2002-01-30 09:03 UTC

  • priority: 5 --> 2
  • status: open --> open-accepted
@lsf37
Copy link
Member Author

@lsf37 lsf37 commented Feb 15, 2015

Commented by nobody on 2002-01-31 02:53 UTC
Logged In: NO

On trying to workaround the bug, I discovered that it was
indeed an extra space that triggered the problem, but I
couldn't figure out how to add to the bug report in time to
add that information. The resolution does indeed correspond
to the problem I encountered.

@lsf37
Copy link
Member Author

@lsf37 lsf37 commented Feb 15, 2015

Updated by lsf37 on 2004-04-12 12:26 UTC

  • status: open-accepted --> closed
@lsf37 lsf37 added the bug label Feb 17, 2015
@lsf37 lsf37 modified the milestone: jflex bug Feb 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.