Bug #79368 [Opn->Fbk]: "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 Updated by: nikic@php.net Reported by: php4fan at gmail dot com Summary: "Unexpected end of file" is not an acceptable error message -Status: Open +Status: Feedback Type: Bug Package: *General Issues Operating System: all PHP Version: 7.4.4RC1 Block user comment: N Private report: N New Comment: Please provide a concrete test case. Previous Comments: ------------------------------------------------------------------------ [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* ------------------------------------------------------------------------ [2020-03-11 16:52:35] php4fan at gmail dot com Description: ------------ "Unexpected <whatever>" alone is NEVER an acceptable error message. You have to tell me what you were expecting instead of what you unexpectedly found, like: "Unexpected XXXX. YYY or ZZZ expected". If that is tricky because the spectrum of legal things that could be expected is too broad, then give a hint or some context: "Unexpected X in Y", "Unmatched <this>", "incomplete <that>"... This is especially egregious with "unexpected end of file", which is usually caused by very trivial errors such an unclosed parenthesis, bracket, brace... but becomes impossible to debug with such an uninformative error message. (Unexpected end of file at line 999999 meaning the error can anywhere in a million lines) It's unbelievable that to this day such an error message is still a thing. "Unexpected end of file in 'if' condition / function body / whatever". You can easily do better than just "unexpected end of file". ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=79368&edit=1