Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63857
Return-Path: <theanomaly.is@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 40860 invoked from network); 13 Nov 2012 19:50:13 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 13 Nov 2012 19:50:13 -0000
Authentication-Results: pb1.pair.com header.from=theanomaly.is@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=theanomaly.is@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
X-PHP-List-Original-Sender: theanomaly.is@gmail.com
X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com  
Received: from [209.85.217.170] ([209.85.217.170:62413] helo=mail-lb0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 03/97-30200-274A2A05 for <internals@lists.php.net>; Tue, 13 Nov 2012 14:50:11 -0500
Received: by mail-lb0-f170.google.com with SMTP id j14so90533lbo.29
        for <internals@lists.php.net>; Tue, 13 Nov 2012 11:50:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        bh=qw/MjnznBf+JWJhK1Q3lKORSHZGk+AnUNbnoXLEx1JM=;
        b=b4oMD7jIzGK7ZIilTKAXwbuQsCsET8hhUp2yGNUTo7aRyRGtATCvWIbne5QL4/+uGS
         UNTpLdxsH1pduOQL/jmErXwdtylE3JyN42G7s2iWiF0sjK58BdJhhrSFHnl4UI6PA8Rk
         sJP5tHUSF1/1ip2bHoPaq2AGFYHNj48fxuiqHneZj4qIuVmONIDn1kP8M5PjTupaI9gM
         c0kfM0MA9oEzIT3/PKsquR5LDTV1H9GfkPec85/4dhHGBYB9F+OLyOmVUhJpDF6fzjsC
         ha6Fw72wI9/UKSO3YuiwHOvLF/35NFGyb/c4MOT5N40dooNQl6IrAQxhFsy3sIauH52K
         tNnQ==
MIME-Version: 1.0
Received: by 10.112.42.34 with SMTP id k2mr2171588lbl.26.1352836206207; Tue,
 13 Nov 2012 11:50:06 -0800 (PST)
Received: by 10.112.24.37 with HTTP; Tue, 13 Nov 2012 11:50:06 -0800 (PST)
In-Reply-To: <CADajX4DAoHvnT2u4TPydh+=X7JKU4zUJSY9SQfGVdObQhwfJvg@mail.gmail.com>
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>
	<8A8A29F9E43E417FB5450D63019B2DDB@NeiRoze>
	<8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.com>
	<CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com>
	<CADajX4DAoHvnT2u4TPydh+=X7JKU4zUJSY9SQfGVdObQhwfJvg@mail.gmail.com>
Date: Tue, 13 Nov 2012 14:50:06 -0500
Message-ID: <CAL+t6cH1uWN6G-No7kRrwVW7Vh3-QH6HpvrR3onRtQmsJLjFRA@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: theanomaly.is@gmail.com (Sherif Ramadan)

On Tue, Nov 13, 2012 at 11:17 AM, Adam Harvey <aharvey@php.net> wrote:
> On 14 November 2012 00:07, Anthony Ferrara <ircmaxell@gmail.com> wrote:
>> There's one important thing that I think you all are missing here. You k=
eep
>> bringing up that we should just use the normal "deprecation" process. Th=
e
>> problem is that the deprecation process was never designed for a feature
>> like this.
>
> Serious question: what was it designed for, then? This (along with
> magic quotes, and register globals) was always what I had in the back
> of my mind when it was being discussed.
>
> <snip>
>> Now, look at ext/mysql. The landscape is completely different. Major
>> projects still rely on it in their most recent versions. Wordpress's lat=
est
>> trunk uses ext/mysql. And as was said here, it's not a trivial change to
>> switch from mysql to mysqli or PDO. ext/mysql is still very heavily reli=
ed
>> upon.
>
> Last time I checked, WordPress's trunk also emulated magic quotes. Old
> code is old. With all due respect to the WP developers, they've made a
> very deliberate choice to maintain extreme backward compatibility
> because their plugin ecosystem demands it. Ultimately, they'll
> presumably emulate mysql_* in userland if it's that important to them,
> just as they are with magic quotes.
>
> I don't think we should let that stop us from removing dead code, or
> replacing APIs that promote antipatterns.
>
>> What I would suggest, is not adding E_DEPRECATED for 5.5. Instead,
>> officially deprecate it in the docs. Then start a PR campaign to get
>> projects like WP to switch away from it. Get the word out there as much =
as
>> possible. Then in 1 to 2 years when 5.6/6 is released, add E_DEPRECATED.
>
> It's already deprecated in the documentation, really =97 I doubt adding
> the actual word "deprecated" will make a difference.
>
> If we're going to drag this out, I'd rather spend an extra year with
> PHP actually generating warnings, as I said upthread.

I'm with you 100% on this. Wasting *yet another few years* on telling peopl=
e...

"hey, soon we will actually begin to discussing, thinking, of taking
action about maybe deprecating the functions officially in an official
manner by which we mean actually throwing the warnings this time, but
for real now not just in the documentation... Seriously, we're not
joking this time..."

Please, this has been dragged out long enough. Give them the warning,
let the next few years push those with dependency issues into forcing
support on their upstreams.

Software must be tolerant of failure and capable of reiteration if it
is to strive. I truly think this "should we or should we throw
E_DEPRECATED" back-and-forth business is rather silly. It's not like
E_DEPRECATED is going to cause every PHP code base on earth to
suddenly and spontaneously combust over night. We are talking about a
version of PHP that will probably take half of these projects the next
3 years to upgrade to (in terms of the majority of their user bases).
By then they're not even using a version of PHP where the extension
has been removed yet. Come on, I mean the wordpress guys are showing
statistics that a 3rd of their entire user base is still using PHP 5.2
for crying out loud. Let's not over-dramatize this thing.

>
> Adam
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>