Don't silence fatal errors with @ #3685
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the silencing operator
@
is used, the intention is generally to silence expected warnings or notices. However, it currently also silences fatal errors. As fatal errors also abort request execution, the result will often be a hard to debug white screen of death.This patch changes the behavior of
@
to only silence warnings, notices and other low-level diagnostics. The following error types will no longer be silenced:There are two main implications for backwards compatibility:
error_reporting()
(orini_set()
) to do so.error_reporting() != 0
to detect silencing. This should be changed toerror_reporting() & $err_no
to detect whether the specific error type is silenced.