Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64107
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50B7370A.4010504@gmail.com>
References: <CADajX4BRUFUb_Wp2a40d2vwXHeMmO611Sqrv7=oxbLHag9qOyg@mail.gmail.com>
	<CADajX4B3RctPoodShRhLLyDQW8-QFaCBOU+6PjL0FDHPGYBtzg@mail.gmail.com>
	<50B5D992.30609@lsces.co.uk>
	<CAOc_q_wvWRHDMy3urOzX4ksSvj--vE2D2AS8mrH8H=q5ZzQjHw@mail.gmail.com>
	<CAEZPtU6Pe_McfMU=zzvL3ap5ys0EVKug=G4TcpgmBc9JSsrDiQ@mail.gmail.com>
	<0B09D94D-3BBC-491C-8E9D-74384E30383D@roshambo.org>
	<50B65363.4020100@gmail.com>
	<50B69797.5030209@gmail.com>
	<50B7370A.4010504@gmail.com>
Date: Thu, 29 Nov 2012 12:17:22 -0500
Message-ID: <CAAyV7nEMwAsQ=3dEmw9D34qhgiTYxuzPD5XrJYy0jbFA6oUJJQ@mail.gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Cc: David Muir <davidkmuir@gmail.com>, Philip Olson <philip@roshambo.org>, 
	Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec54fb9c6c498c804cfa574da
Subject: Re: [PHP-DEV] ext/mysql in PECL and E_DEPRECATED
From: ircmaxell@gmail.com (Anthony Ferrara)

--bcaec54fb9c6c498c804cfa574da
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Angel

On Thu, Nov 29, 2012 at 12:02 PM, =C1ngel Gonz=E1lez <keisial@gmail.com> wr=
ote:

> David Muir wrote:
> > On 29/11/12 05:09, =C1ngel Gonz=E1lez wrote:
> >> I see it as simple to show E_DEPRECATED but not when installed from
> >> PECL.
> >>
> >> 1) Add a
> >> int mysql_extension_triggers_deprecated_warning =3D 1;
> >>
> >> And use it as a conditional for triggering the warning.
> >>
> >> 2) Copy the extension code to PECL
> >>
> >> 3) Add these changes in PECL
> >> - If the mysql functions are not already registered,
> >> register them with the bundled code.
> >> - Set mysql_extension_triggers_deprecated_warning =3D 0;
> >>
> >> 4) That's it.
> >>
> >
> > Then people (distros, hosts, etc) will just install it from PECL
> > instead to avoid all the E_DEPRECATED mess.
> >
> > David
> That's the goal.
> If they really want the extension they can install it from PECL and they
> don't get the E_DEPRECATED since that's not coming from core.
>
> No triggers-warning, moves-to-PECL, no-longer-triggers.
>
> It also provides a supported procedure for installing ext/mysql other
> than patching php to skip the warning. When someone complains about how
> they can only use ext/mysql (eg. they are using a code-protected script
> which uses ext/mysql and is critical for their business...), you can
> point to PECL, as well as explaining how it doesn't have the same
> guarantees as php core.


Just pointing this out: that's NOT what this RFC recommends, and is NOT
what's being voted on. This RFC is talking about ONLY adding E_DEPRECATED
to core. And the way it's proposed to be done, the "moves-to-PECL" couldn't
happen, since it's hard-coded into the core extension...

So be careful what you're voting for...

--bcaec54fb9c6c498c804cfa574da--