Re: RFC: ext/mysql deprecation
| From: | Johannes Schlüter | Date: | Wed, 14 Nov 2012 09:24:56 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63866@lists.php.net to get a copy of this message | ||
On Tue, 2012-11-13 at 22:42 -0800, Stas Malyshev wrote:
> Hi!
>
> >> 2. Mention how to turn off E_DEPRECATED warnings in the RFC?
> >
> > Done and done. I've added a (short) workarounds section towards the
> > bottom, which can be moved up later if the RFC is accepted.
>
> Please note currently PHP has no mechanism of turning off any warnings
> or errors. The best you can do is to cause them not be printed. However,
> any tool that intercepts error messages still sees them, they still
> consume resources when produced, still may break unit tests if you're
> not aware of them and they convert errors to failures like PHPUnit does,
> still will break any code that sets it's won error reporting if it
> doesn't remember to disable deprecated messages, etc. So adding warnings
> hurts performance and may hurt functionality even if you don't see them.
If PHPUnit breaks on E_DEPRECATED by default I would consider it broken.
(But I see your point)
johannes
--
Johannes Schlüter, MySQL Connectors Team, ORACLE Corporation