Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
MIME-Version: 1.0
Sender: patrick.allaert@gmail.com
In-Reply-To: <50B5D992.30609@lsces.co.uk>
References: <CADajX4BRUFUb_Wp2a40d2vwXHeMmO611Sqrv7=oxbLHag9qOyg@mail.gmail.com>
	<CADajX4B3RctPoodShRhLLyDQW8-QFaCBOU+6PjL0FDHPGYBtzg@mail.gmail.com>
	<50B5D992.30609@lsces.co.uk>
Date: Wed, 28 Nov 2012 15:50:47 +0100
Message-ID: <CACwt+JeuSo7TOyVLUMhvQPx2duPi9aDw=HZ=qgknKi+5kVP8VA@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: [VOTE] ext/mysql deprecation in 5.5
From: patrickallaert@php.net (Patrick ALLAERT)

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