Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: X10 2.1.2
-
Fix Version/s: None
-
Component/s: X10 Compiler: Front-end Parser
-
Labels:None
-
Environment:Windows XP/Cygwin
-
Number of attachments :
Description
The following code produces error message for the line before the actual error, which is quite misleading, because general intuition about parsers is that the first message has the most relevant information.
Besides, the error message for the actual error is not helpful.
class IncorrectByteSuffix {
static def run() {
assert (2u as Byte) == 2b;
}
}
The error message (as of X10 2.1.2) is
...\IncorrectByteSuffix.x10:2: Syntax error: Token "{" expected instead of this input ...\IncorrectByteSuffix.x10:4: Syntax error: Unexpected input ignored: "ERROR_TOKEN" 2 errors.
Issue Links
- duplicates
-
XTENLANG-1814
Confusion over point deconstructing syntax leads to spurious parse error
-
-
XTENLANG-1841
Spurious initial error message when method body doens't parse
-
-
XTENLANG-2647
'instead of this input' parse errors could be better
-
This is covered by XTENLANG-1814, XTENLANG-1841, and XTENLANG-2647.