I believe it is actually just referring to end of file. With a missing closing parenthesis like that, the parser is consuming the rest of the script file looking for another parenthesis. It might be possible to catch this earlier on (e.g., if it encounters a closing curly brace before it finds the matching parenthesis). I'm not sure if there's already an issue in the tracker for that or not, but there probably should be.