|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2020-11-13 18:49 UTC] php4fan at gmail dot com
[2021-02-05 21:44 UTC] cmb@php.net
-Status: Open
+Status: Duplicate
-Package: *General Issues
+Package: Scripting Engine problem
-Assigned To:
+Assigned To: cmb
[2021-02-05 21:44 UTC] cmb@php.net
|
|||||||||||||||||||||||||||
Copyright © 2001-2024 The PHP GroupAll rights reserved. |
Last updated: Fri Apr 19 08:01:28 2024 UTC |
Description: ------------ The script below rightfully results in a parse error, but the error message is garbage. It says 'unexpected token "<"' (so far so good) but then it adds "expecting end of file". End of file is only one out of a pile of possible valid tokens there. I appreciate that you tried to improve on previous versions which would only say "unexpected token [...]" without specifying what valid thing was expected. I myself complained many times about that. It's necessary to always specify not only the unexpected thing but also what was expected instead, at least when the range of possibilities can be reasonably narrowed down. But it makes no sense to name only one random possible valid token and to say you are expecting that one. If the range of valid possibilities is too big to list, just say so. Test script: --------------- <?php echo 3+2; // I'll forget a closing php tag ("? >") now <body> </body> <?php // ... ?> Expected result: ---------------- Parse error: syntax error, unexpected token "<", ... and there you could end with something like: "expecting end of file among other valid possibilities", or "expecting something else (too many possibilities to list them exhaustively)" (and of course "on line 7") Actual result: -------------- Parse error: syntax error, unexpected token "<", expecting end of file in [...] on line 7