c39150e6bb
this needs a string comparison because there seems to be no other way to get that information out of bison. usually the location info is going to be correct (pointing at a bad token), but since EOF isn't a token as such it'll be wrong in that this case. this hasn't shown up much so far because a single line ending *is* a token, so any file formatted in the usual manner (ie, ending in a line ending) would have its EOF position reported correctly. (cherry picked from commit 855fd5a1bb781e4f722c1d757ba43e866d370132) Change-Id: I120c56a962f4286b1ae3b71da7b71ce8ec3e0535
5 lines
193 B
Text
5 lines
193 B
Text
error: syntax error, unexpected end of file, expecting '"'
|
|
at «stdin»:3:6:
|
|
2| # Note that this file must not end with a newline.
|
|
3| a 1"$
|
|
| ^
|