Closed GoogleCodeExporter closed 9 years ago
Yup - I noticed this when adding that arc type.
Using a space is one workaround, putting double quotes around the entity name
is the other e.g. "A"x-"B". It doesn't look easy to fix up the scanner as it
doesn't know the grammar context at that point so any string handling would
take effect for each and every string in the input.
So I've opted to improve the error message output as you suggest. Now it
detects if "x-" appears on the line where the parse failed and adds a note to
the output as well as displaying the faulty input line:
Error detected at line 22: syntax error, unexpected characters.
> ax-b [label="data2"];
Note: This input line contains 'x-' which has special meaning as a
'lost message' arc, but may not have been recognised as such if it
is preceeded by other letters or numbers. Please use double-quoted
strings for tokens before 'x-', or insert a preceeding whitespace if
this is what you intend.
Original comment by Michael....@gmail.com
on 4 Oct 2010 at 8:55
Fixed at r145
Original comment by Michael....@gmail.com
on 4 Oct 2010 at 8:58
Original issue reported on code.google.com by
NThykier@gmail.com
on 19 Sep 2010 at 3:14