Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64108
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <q70fb8p8h1662v7ofui6pp2nfo6ifl1ng5@4ax.com>
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>
	<CAAyV7nGoV0Q78V6sRTNkiwsj3mZDWdJyFpDgexPe7r7B4xe8=A@mail.gmail.com>
	<CAKOpQSzyCjMH2Rvo4n0kgbugzvwRga4SnO4URR2uqoTefG3Z6g@mail.gmail.com>
	<q70fb8p8h1662v7ofui6pp2nfo6ifl1ng5@4ax.com>
Date: Thu, 29 Nov 2012 09:28:58 -0800
Message-ID: <CAKOpQSy+2jx56gnyV-u0eKB9BfUmnT7CTZ7f5hek9P0=4mdxQA@mail.gmail.com>
To: Jan Ehrhardt <phpdev@ehrhardt.nl>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=e89a8f2350974a85de04cfa59ec3
Subject: Re: [PHP-DEV] Re: [VOTE] ext/mysql deprecation in 5.5
From: kris.craig@gmail.com (Kris Craig)

--e89a8f2350974a85de04cfa59ec3
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 29, 2012 at 7:46 AM, Jan Ehrhardt <phpdev@ehrhardt.nl> wrote:

> Kris Craig in php.internals (Wed, 28 Nov 2012 12:33:55 -0800):
> >We also know that E_DEPRECATED works when other approaches do not.  I
> would
> >point you all to the famous example of Drupal 7, which would break
> >completely due to a flurry of E_DEPRECATED warnings (if display_errors was
> >set to on) being triggered as of 5.3 due to their continued use of
> >magic_quotes_gpc and magic_quotes_runtime.  When Drupal 8 was released
> some
> >time later, the code was fixed so that it no longer used those out-dated
> >functions.
>
> http://drupal.org/community-initiatives/drupal-core
> Drupal 8 will not be released before August 2013. Maybe in the current
> core the E_DEPRECATED warnings are gone, but certainly not in many of
> the modules.
>
> People are still switching to Drupal7. And Drupal7 throws the watchdog
> full with E_DEPRECATED warnings when it is running onder PHP5.4. The
> views module has issues with PHP 5.4, but some modules even let Drupal7
> under PHP5.4 crash completely:
> http://drupal.org/node/1831402
>
> If E_DEPRECATED stays in ext/mysql even after it has moved to PECL, the
> result will be that more and more people turn E_DEPRECATED warnings off.
>

I think you're forgetting though that the same applies to PHP itself.  Many
repos still default to PHP 5.1.x.  Adoption always tends to be a lagging
factor.  I don't see any evidence to suggest that Drupal and other distros
have even slower adoption rates than PHP.  In fact, the opposite seems to
be true from what I've observed.

In other words, most of these people you referenced who are still using
Drupal 6 are probably still using an older version of PHP as well.
 Therefore, most people using Drupal 7 probably don't have to worry about
the deprecation because they haven't upgraded to 5.3.3+ yet.  But it did
affect enough people that it forced the Drupal devs to update their code to
conform to the changes in PHP.

We shouldn't be targetting future PHP releases to sync with older distros
simply because many people still use them.  Given that most people tend to
use older versions of PHP as well, I believe it's safe to say that the two
cancel one another out.

--Kris

--e89a8f2350974a85de04cfa59ec3--