Re: PHP 4.0 Bug #1531 Updated: require() causes flex scanner error
| From: | Zeev Suraski | Date: | Sat, 10 Feb 2001 18:35:47 +0000 |
| Subject: | Re: PHP 4.0 Bug #1531 Updated: require() causes flex scanner error | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-46189@lists.php.net to get a copy of this message | ||
As it should... This bug should be closed.
At 20:25 10/2/2001, jimw@php.net wrote:
ID: 1531 Updated by: jimw Reported By: graeme@kc.co.nz Status: Open Old-Bug Type: Feature/Change Request Bug Type: Scripting Engine problem Assigned To: Comments: 4.0 still gives the same message. Previous Comments: --------------------------------------------------------------------------- [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 --------------------------------------------------------------------------- [1999-06-20 21:06:01] jim@cvs.php.net Zeev knows about this one, and I believe it will be fixed in PHP4. There may actually be a very old bug on this as well. --------------------------------------------------------------------------- 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 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/