Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63835
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50A20CCB.8090909@lsces.co.uk>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
	<50A10A9D.9070402@oracle.com>
	<CAAyV7nF2tt6HtFZKevH_2kknqOvEmLJjEOF2_Bn_VHaZFUJERw@mail.gmail.com>
	<CAPwsocH3_qHSZbLFe27qX+KgBAC1D8KhwLi+PLHW503sCTBtTw@mail.gmail.com>
	<50A1946F.8010407@lerdorf.com>
	<50A20CCB.8090909@lsces.co.uk>
Date: Tue, 13 Nov 2012 10:13:44 +0000
Message-ID: <CAPwsocGruK=Hp3zgrVVYH1J0LyoXRtdK=VzCX+nevE-HqVTsXg@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>, Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: leight@gmail.com (Leigh)

Hi

On 13 November 2012 00:29, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> That is simply not true. If you download PHP and do ./configure && make
> install you do not get MySQL support. You have to explicitly specify
> that you want it.

My apologies then. I actually checked a ./configure output, and saw
under Configuring extensions "checking for MySQL support... no"

I assumed it was going to try to enable it if it was available. Lots
of other extensions have the wording "checking whether to enable",
which is why I differentiated it from those.

On 13 November 2012 09:03, Lester Caine <lester@lsces.co.uk> wrote:
> YES people can simply switch off the checks, but again that misses the whole
> problem! Having switched off the checks - you have no idea what is about to
> blow up.

If users wish to deliberately ignore (or worse, specifically disable)
informative messages during development, that is their own problem.
When ext/mysql is finally removed, nobody will be able to say they
didn't have enough warning.

The sooner we get this warning out there (i.e. E_DEPRECATED + message
in the documentation starting with 5.5), the sooner wider community
can start adjusting for it. There is no point delaying it as much as
possible. As Sherif said, there has been far too much procrastination
on the subject already.

Lets get E_DEPRECATED in for the first RC so all of the social-focused
php sites can get their rants out early, and get a few users thinking
about the future of their codebases as soon as possible. Maybe even
some of them will decide to contribute back and write some adoption
guides and/or cheat sheets.