Doc #76318 [Opn->Ver]: Unclear statement in set_error_handler docs
| From: | girgias@php.net | Date: | Tue, 01 Jan 2019 22:09:50 +0000 |
| Subject: | Doc #76318 [Opn->Ver]: Unclear statement in set_error_handler docs | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-16268@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=76318&edit=1
ID: 76318
Updated by: girgias@php.net
Reported by: teo8976 at gmail dot com
Summary: Unclear statement in set_error_handler docs
-Status: Open
+Status: Verified
Type: Documentation Problem
Package: Documentation problem
PHP Version: Irrelevant
Block user comment: N
Private report: N
Previous Comments:
------------------------------------------------------------------------
[2018-05-09 18:12:07] teo8976 at gmail dot com
Description:
------------
---
From manual page: http://www.php.net/function.set-error-handler
---
This sentence:
"""
The following error types cannot be handled with a user defined function: E_ERROR, E_PARSE,
E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING, and most of E_STRICT raised in the
file where set_error_handler() is called
"""
is ambiguous. It is unclear whether the part that says "raised in the file where
set_error_handler() is called" applies only to E_STRICT, or to all the mentioned error levels.
That is, one could interpret:
A)
""
The following error types cannot be handled with a user defined function:
- E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING (wherever they
are raised)
- most of E_STRICT raised in the file where set_error_handler() is called
""
or
B)
""
The following error types cannot be handled with a user defined function:
{E_ERROR, E_PARSE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING and most of
E_STRICT}
raised in the file where set_error_handler() is called
""
From what I've been able to test, it seems that the truth is (A)
This must be made clearer.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=76318&edit=1