ID: 33637
Updated by: [EMAIL PROTECTED]
Reported By: michal at cihar dot com
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Linux
PHP Version: 4.3.10
New Comment:
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.
Thank you for the report, and for helping us make our documentation
better.
"Be warned that parse error in included file doesn't cause processing
halting in PHP versions prior to PHP 4.3.5."
Previous Comments:
------------------------------------------------------------------------
[2005-07-11 12:00:14] [EMAIL PROTECTED]
The note you're referring to tells about exactly this change: the
behaviour changed in 4.3.5 both for include() and require().
------------------------------------------------------------------------
[2005-07-11 11:19:49] michal at cihar dot com
Well it didn't happen before :-)
------------------------------------------------------------------------
[2005-07-11 11:03:55] [EMAIL PROTECTED]
Parse error halts processing in any case, because it's parse error.
Reclassified.
------------------------------------------------------------------------
[2005-07-11 00:09:01] michal at cihar dot com
Sorry, the quotation was too short, it should have been:
"Be warned that parse error in required file doesn't cause processing
halting in PHP versions prior to PHP 4.3.5. Since this version, it
does."
------------------------------------------------------------------------
[2005-07-11 00:06:00] michal at cihar dot com
I've read the documentation! There is:
"Be warned that parse error in required file doesn't cause processing
halting in PHP versions prior to PHP 4.3.5."
It's about required and not about included files. Please either make
the documentation clear that the same applies to included file or make
interpreter not to fail on this.
------------------------------------------------------------------------
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
http://bugs.php.net/33637
--
Edit this bug report at http://bugs.php.net/?id=33637&edit=1
