PHP 4.0 Bug #1531 Updated: require() causes flex scanner error

ID: 1531 Updated by: zeev Reported By: graeme@kc.co.nz Old-Status: Open Status: Closed Bug Type: Scripting Engine problem Assigned To: Comments: intended behavior Previous Comments: --------------------------------------------------------------------------- [2001-02-10 13:25:00] jimw@php.net 4.0 still gives the same message. --------------------------------------------------------------------------- [2000-08-17 11:48:09] hholzgra@php.net BD>> still it should not result in a parse error > It's not parse error, please read the message. > It didn't failed opening, it failed reading. > And require is not allowed to fail. > That's not unknown file, that's known non-file. >-- >Stanislav Malyshev stas@zend.com ok, got it now, i thought it was related to just ./, not directories in general but it fails for include to, while including for example a non-existing file produces the message i cited above and the error message is very misleading so i move this on to feature requests: 1) should give clearer error-message 2) at least include should treat directories like nonexistant (or empty?) files and issue a warning instead of a fatal error --------------------------------------------------------------------------- [2000-08-17 11:21:40] hholzgra@php.net still it should not result in a parse error it should produce a warning PHP Warning: Failed opening './' for inclusion as with other unknown files --------------------------------------------------------------------------- [2000-08-17 11:07:48] stas@php.net I don't see problem here. ./ is not a file, and reading it as a file fails. So it should be. --------------------------------------------------------------------------- [2000-08-17 10:57:52] hholzgra@php.net still there even in 4.0.1 --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=1531&edit=2