Grammatica - Bugs: bug #3929, Parser: Unexpected token error...
You are not allowed to post comments on this tracker with your current authentication level.
bug #3929: Parser: Unexpected token error messages may be misleading
Submitter: | Per Cederberg <cederberg> | ||
Submitted: | Tue 10 Jun 2003 08:53:43 AM UTC | ||
Severity: | 1 - Minor | Item Group: | Software |
Status: | Fixed | Assigned to: | cederberg |
Open/Closed: | Closed |
Tue 10 Jun 2003 04:53:42 PM UTC, comment #2: |
Per Cederberg <cederberg> |
Tue 10 Jun 2003 12:32:15 PM UTC, comment #1: This has been fixed by adding a check for the lookahead token also for the fallback alternative. The fix has been added to both the Java and C# parsers. |
Per Cederberg <cederberg> |
Tue 10 Jun 2003 08:53:43 AM UTC, original submission:
The unexpected token error messages may be misleading in some cases. When a production has a fallback alternative, it will always be selected whether or not it matches the current token or not. This will result in a unexpected token error (which is correct) but with only the expected tokens from the fallback alternative listed (which is incorrect).
|
Per Cederberg <cederberg> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2003-06-10 | cederberg | Open/Closed | Open | None | |
2003-06-10 | cederberg | Status | None | None |
Powered by Savane 3.13-f8d8.
Corresponding source code
Version 1.2 has now been released. Closing this bug.