Re: RFC: ext/mysql deprecation
| From: | David Soria Parra | Date: | Tue, 13 Nov 2012 04:38:51 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63831@lists.php.net to get a copy of this message | ||
On 2012-11-13, Adam Harvey <aharvey@php.net> wrote:
> On 13 November 2012 01:16, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>> On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel <ulf.wendel@oracle.com> wrote:
>>> Don't bother. There is a standard way of deprecation, at least I assume
>>> there is. Its proven. Use it: docs warnings, E_DEPRECATED, remove.
>>
>> I agree to deprecate/remove on the long run, but I think that we should
>> wait for the next version for doing so.
>
> Honestly, if we were going to delay the eventual removal (and I'm not
> sure we should), I'd rather have an extra release cycle with
> E_DEPRECATED, rather than an extra release cycle with
> documentation-only warnings that are more easily ignored ? so either
> way, I'd still want the notices in 5.5.
Personally I think we should E_DEPRECATE it. We will have enough time
till 5.5 RC1 to decide on the RFC within the regular 2-4 weeks.
+1 from me.