error_reporting(): additional info about set_error_handler function would be useful
Nobody has claimed this yet.
- Dominant language
- XML
- Stars
- 596
- Forks
- 890
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 55
Description
What's not immediately clear from https://www.php.net/manual/en/function.error-reporting.php is that even if you set error_reporting to a specific value, if you also set a user-defined error handler function with set_error_handler, errror_reporting() settings will have no effect.
On https://www.php.net/manual/en/function.set-error-handler this is mentioned ("error_reporting() settings will have no effect and your error handler will be called regardless - however you are still able to read the current value of error_reporting and act appropriately.").
I think it would be valuable to add this information to https://www.php.net/manual/en/function.error-reporting.php (e.g. by adding it to the Notes section). I spent quite some time trying to understand why DEPRECATED errors were stopping my program flow, even though I had error_reporting(E_ERROR | E_WARNING | E_PARSE | E_NOTICE); set. It was only when I carefully read https://www.php.net/manual/en/function.set-error-handler that I realized my error_reporting setting was ignored.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the error_reporting() and set_error_handler() manual pages, especially their Notes sections, and compare the existing explanation of user-defined error handlers. Add a clear cross-reference or equivalent note to the error_reporting() page explaining that a custom handler is still called regardless of error_reporting() settings; done means the behavior and relevant limitation are clear to readers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100