Bug #79368 [Com]: "Unexpected end of file" is not an acceptable error message

Edit report at https://bugs.php.net/bug.php?id=79368&edit=1 ID: 79368 Comment by: bugreports at gmail dot com Reported by: php4fan at gmail dot com Summary: "Unexpected end of file" is not an acceptable error message Status: Open Type: Bug Package: *General Issues Operating System: all PHP Version: 7.4.4RC1 Block user comment: N Private report: N New Comment: > And btw, it's not just not closing something that you've opened. > > For example this: > > ``` > <?php > > $s = > ``` surely, you opened an assignment and never finished it so from the view of a parser everyting after it is part of the assignment until ; appears and then averything after "that line" to ; makes little to no sense Previous Comments: ------------------------------------------------------------------------ [2020-03-11 19:17:17] php4fan at gmail dot com > to tell you something specific it needs to be parsed Then how comes you are able to give sensible error messages in other cases? > "Unexpected end of file" is pretty clear! you are opening more stuff with > { as you close with } It could be {, it could be ( or [, even "... and then you have to find which one. And btw, it's not just not closing something that you've opened. For example this: ``` <?php $s = ``` ------------------------------------------------------------------------ [2020-03-11 18:30:33] bugreports at gmail dot com > Well, I expect it to tell me why the input is unparseable to tell you something specific it needs to be parsed > By your reasoning, no userful error message would ever be given by any parser for any syntax > error "Unexpected end of file" is pretty clear! you are opening more stuff with { as you close with } ------------------------------------------------------------------------ [2020-03-11 18:10:51] php4fan at gmail dot com > Please provide a concrete test case. You could have easily created one just with the information provided in my report, but here is one: ``` <?php if( ``` And here's another (see if you can spot the actual error, then imagine it being in a real-life-size file) ``` <p class="comment"> <span class="comment_text"><?php echo $comment->text; ?></span> <?php if (true) { ?> <span class="comment_edit_links"> </span> <? } ?> </p> ``` > how do you imagine a parser giving you somnething useable in case of *unparseable input* Well, I expect it to tell me why the input is unparseable. By your reasoning, no userful error message would ever be given by any parser for any syntax error. ------------------------------------------------------------------------ [2020-03-11 17:44:32] nikic@php.net Please provide a concrete test case. ------------------------------------------------------------------------ [2020-03-11 17:10:35] bugreports at gmail dot com how do you imagine a parser giving you somnething useable in case of *unparseable input* ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=79368 -- Edit this bug report at https://bugs.php.net/bug.php?id=79368&edit=1