Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53877
Return-Path: <ava3ar@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 93793 invoked from network); 11 Jul 2011 15:11:47 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 11 Jul 2011 15:11:47 -0000
Authentication-Results: pb1.pair.com header.from=ava3ar@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=ava3ar@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
X-PHP-List-Original-Sender: ava3ar@gmail.com
X-Host-Fingerprint: 209.85.220.170 mail-vx0-f170.google.com  
Received: from [209.85.220.170] ([209.85.220.170:33381] helo=mail-vx0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 87/13-09103-0B21B1E4 for <internals@lists.php.net>; Mon, 11 Jul 2011 11:11:46 -0400
Received: by vxi39 with SMTP id 39so3112129vxi.29
        for <internals@lists.php.net>; Mon, 11 Jul 2011 08:11:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=lBbq5KInGrLp+2BSKoAYNeWkjZ7Cg06BmQ+ZJfxbrLQ=;
        b=xLioeihKoB//LPLHXcJxgT7yG2EYGoAzWpGdY4L0dq6FnVrD6Oa1hO+a61rfVF20x5
         Ou13vRA1sgqBeKKcUIF8QaWPA4tIlUdlmz2z8Ifkd/oRFl4PnjHUEcQgmkl8zRMmipC3
         A0hseJP8B8HcTceNOI4MeeV+NjOQnMeZT9Eu8=
Received: by 10.52.170.205 with SMTP id ao13mr2366029vdc.509.1310397101171;
 Mon, 11 Jul 2011 08:11:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.72.68 with HTTP; Mon, 11 Jul 2011 08:11:21 -0700 (PDT)
In-Reply-To: <CADajX4AMRqYMd=r+eiOGuvRZ8jSw88SKPXAb7AtemW-_hi097Q@mail.gmail.com>
References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> <CADajX4AMRqYMd=r+eiOGuvRZ8jSw88SKPXAb7AtemW-_hi097Q@mail.gmail.com>
Date: Mon, 11 Jul 2011 16:11:21 +0100
Message-ID: <CAF=va1U4bSzV6RQ_pDOTrU3JRCDM6YSm=PE5-sa-u1wNW8i24w@mail.gmail.com>
To: Adam Harvey <aharvey@php.net>
Cc: Philip Olson <philip@roshambo.org>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec53f9763bae5f904a7cc99c2
Subject: Re: [PHP-DEV] deprecating ext/mysql
From: ava3ar@gmail.com (Keloran)

--bcaec53f9763bae5f904a7cc99c2
Content-Type: text/plain; charset=ISO-8859-1

maybe we should get another E_, E_NEARLY_DEPRECATED that way we can set this
to that, and then 5.5 we can move it to E_DEPRECATED, that way people have
to go read the docs, the amount of people even those who have been in the
field for years, that dont know about php.net/<func> and still look stuff up
on google makes me wonder that no matter how soft you make the change by
doing it in the docs, wont make that much difference to how people react to
it being dropped

On Mon, Jul 11, 2011 at 3:40 PM, Adam Harvey <aharvey@php.net> wrote:

> On 11 July 2011 01:03, Philip Olson <philip@roshambo.org> wrote:
> > What this means to ext/mysql:
> >
> >  - Softly deprecate ext/mysql with education (docs) starting today
> >  - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0
> >  - Add pdo_mysql examples within the ext/mysql docs that mimic the
> current
> >   examples, but occasionally introduce features like prepared statements
> >  - Focus energy on cleaning up the pdo_mysql and mysqli documentation
> >  - Create a general "The MySQL situation" document that explains the
> situation
>
> I'm hugely +1 on this. (Which won't be a shock to anyone on IRC.) It's
> time to start softening the user base up for the idea that, one day,
> ext/mysql will in fact go away, and probably won't be terribly
> mourned.
>
> Adam
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec53f9763bae5f904a7cc99c2--