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.

Sign up for GitHub

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

Jump to bottom

Better reporting of invalid type definitions #17

Closed
GoogleCodeExporter opened this issue Oct 14, 2015 · 1 comment
Closed

Better reporting of invalid type definitions #17

GoogleCodeExporter opened this issue Oct 14, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

In TypeParseIdentPart, I added TokenEOF, TokenComma, TokenCloseBracket, and
TokenSemicolon as loop terminations (like the present default case does).
The new default case now reports an error saying it's an invalid type
definition

Original issue reported on code.google.com by [email protected] on 2 Jun 2009 at 12:49
@GoogleCodeExporter
Copy link
Author 

Existing code looks ok to me. Maybe I need a better failure report.

Original comment by [email protected] on 3 Jun 2009 at 5:55

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter