Re: Re: [VOTE] ext/mysql deprecation in 5.5
| From: | Patrick ALLAERT | Date: | Wed, 28 Nov 2012 14:50:47 +0000 |
| Subject: | Re: Re: [VOTE] ext/mysql deprecation in 5.5 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-64075@lists.php.net to get a copy of this message | ||
2012/11/28 Lester Caine <lester@lsces.co.uk>:
> There is no 'objection' to deprecating the extension, but adding
> E_DEPRECATED to the code is problematic since that should NOT be present in
> a PECL version of the code?
Sorry, but removing the E_DEPRECATED notice when moved to PECL is not
part of the proposed RFC and should certainly not happen.
If ext/mysql is deprecated, it can perfectly live in PECL while
remaining deprecated. There ARE (supported) replacements for ext/mysql
and even if someone really one to use it, it should still be
considered deprecated regardless of the repository holding the code.
> Adding it in one location and not the other does
> not make sense.
Absolutely! There is no reason to remove that kind of notice in the future.
--
Patrick