Re: Deprecation of the Error Control Operator (@ symbol)
| From: | Sara Golemon | Date: | Tue, 05 Jan 2016 17:48:11 +0000 |
| Subject: | Re: Deprecation of the Error Control Operator (@ symbol) | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-90116@lists.php.net to get a copy of this message | ||
On Tue, Jan 5, 2016 at 3:57 AM, Zeev Suraski <zeev@zend.com> wrote:
>> From: Derick Rethans [mailto:derick@php.net]
>> That's going to mean an INI setting.. that hosters could abuse.
>> Having an INI setting like this as part of core is IMO not a great idea.
>
I honestly don't understand why that's a bad idea. There are a LOT of
settings that hosters could abuse, but as a general rule they don't,
because it breaks client apps and clients leave.
A hoster could just as easily install XDebug and turn that setting on.
Are they doing that?
Or are you, Derick Rethans, suggesting that installing XDebug is a bad idea? ;)
> I agree. Perhaps through a declare() statement instead? We could easily
> make it file-based, so that the declare() statement only affects the local
> file, or we could make it global for the entire request.
>
Eh, feels very tomato-tomato to me. Trading in a line in
php.ini/.htaccess/index.php for a line in index.php. Ultimately I'm
the wrong person to defend this since I don't personally have a need
for it, I was just trying to offer compromises.
For context, I do believe the person suggesting it was thinking in
terms of "Finding that fatal error that's been supressed."
-Sara