Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64077
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error)
Message-ID: <50B63C34.3040800@lsces.co.uk>
Date: Wed, 28 Nov 2012 16:30:44 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CADajX4BRUFUb_Wp2a40d2vwXHeMmO611Sqrv7=oxbLHag9qOyg@mail.gmail.com> <CADajX4B3RctPoodShRhLLyDQW8-QFaCBOU+6PjL0FDHPGYBtzg@mail.gmail.com> <50B5D992.30609@lsces.co.uk> <CACwt+JeuSo7TOyVLUMhvQPx2duPi9aDw=HZ=qgknKi+5kVP8VA@mail.gmail.com>
In-Reply-To: <CACwt+JeuSo7TOyVLUMhvQPx2duPi9aDw=HZ=qgknKi+5kVP8VA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [VOTE] ext/mysql deprecation in 5.5
From: lester@lsces.co.uk (Lester Caine)

Patrick ALLAERT wrote:
> 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.

Then perhaps a few more people will start complaining as well then. There is NO 
reason to have deprecated messages on legacy packages in PECL no other older 
packages have them? So why pick out this one?

This NOT the way to handle retiring well used legacy extensions and it just gets 
in the way of using E_DEPRECATED when it IS needed! At the very minimum we 
should be able to ignore warnings when they are well understood without having 
to hide everything else as well :(

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk