Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63823
Return-Path: <tyra3l@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 62455 invoked from network); 12 Nov 2012 17:16:31 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Nov 2012 17:16:31 -0000
Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
X-PHP-List-Original-Sender: tyra3l@gmail.com
X-Host-Fingerprint: 209.85.160.42 mail-pb0-f42.google.com  
Received: from [209.85.160.42] ([209.85.160.42:59824] helo=mail-pb0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 2F/80-57791-CEE21A05 for <internals@lists.php.net>; Mon, 12 Nov 2012 12:16:29 -0500
Received: by mail-pb0-f42.google.com with SMTP id rp2so835513pbb.29
        for <internals@lists.php.net>; Mon, 12 Nov 2012 09:16:26 -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;
        bh=Hhqvne1i9aeT5d8nqsuSjvD4Iy7P+oFrf+IrSn9ZUAM=;
        b=WLlkAY6m8R8P5jR4fWgg+gi4vzOcJn0OhRXdj3yPKLUAvew1/9gja4csn7BiknKM27
         jK7lLMIe6GguAs1M+koBE7WFFPWr4pvZmA9pJZWHlQRHXhFALAVGky70S64/RjGIqQ7J
         9VMCncUa2rOITenHPQvpYs/PfnlNgV3v5ZCKVBFrtq+zY1GKXdq9rcyCzT/jsPbpUUze
         0pRIzq76pfEHGJ5saOvVVEW2xMk6ocHuvB3UfWEJzflu4DFgl0hNUrQAFFLz5BrinIWF
         MdqXWkpGf1Rg1ijWHFbtWVnlY0nHGkTizZV/SmlDmUD4p++aLNIXYNNCt3XHiCNnLRO0
         2y2g==
MIME-Version: 1.0
Received: by 10.68.237.167 with SMTP id vd7mr52985042pbc.161.1352740586247;
 Mon, 12 Nov 2012 09:16:26 -0800 (PST)
Received: by 10.68.247.202 with HTTP; Mon, 12 Nov 2012 09:16:26 -0800 (PST)
In-Reply-To: <50A10EF1.1010405@oracle.com>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
	<50A0F797.30604@daylessday.org>
	<CADajX4DimWGtWp7Af-XgSjU2E4G0ZTwryt4zQXiumb3wtZe60g@mail.gmail.com>
	<50A10C43.2000704@daylessday.org>
	<50A10EF1.1010405@oracle.com>
Date: Mon, 12 Nov 2012 18:16:26 +0100
Message-ID: <CAH-PCH4e6ECSybUFCX=tA+2OB6+j=G8utnhPcMvaQZn3Mc_fQw@mail.gmail.com>
To: Ulf Wendel <ulf.wendel@oracle.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b3390251dd60504ce4f766c
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b3390251dd60504ce4f766c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel <ulf.wendel@oracle.com> wrote:

> Am 12.11.2012 15:48, schrieb Antony Dovgal:
>
>  On 2012-11-12 18:15, Adam Harvey wrote:
>>
>>> I don't think the documentation is necessarily effective here,
>>> particularly with functions that users tend to know by heart
>>>
>> <skip>
>>
>>> I'm not really convinced the average user ever looks at the manual for
>>> things they know, truth be told.
>>>
>>
>> Well, I'd expect people actively developing applications in PHP to use
>> the docs from time to time.
>> But my concern is for people using legacy apps.
>> True, they might not use the docs at all and the only warning they'll
>> get when they do
>> their usual PHP upgrade is error logs stuffed full of E_DEPRECATED.
>> So what is they going to do in that case? Disable the notice, of course.
>>
>
>
> Don't bother. There is a standard way of deprecation, at least I assume
> there is. Its proven. Use it: docs warnings, E_DEPRECATED, remove.
>
> Ulf
>
>
Hi,

I agree to deprecate/remove on the long run, but I think that we should
wait for the next version for doing so.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7b3390251dd60504ce4f766c--