Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71449
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
Sender: are.you.winning@gmail.com
In-Reply-To: <7E.A3.39789.25841E25@pb1.pair.com>
References: <CAGa2bXZJoyV+9qN6v8j3+vHexoqDtHR4cZkgdtdc1GpVkDaD9w@mail.gmail.com>
	<CAGa2bXY4=3UVDVdR=curS96r=pvTrxDYA0wgy+k7X46omtTPgQ@mail.gmail.com>
	<7E.A3.39789.25841E25@pb1.pair.com>
Date: Thu, 23 Jan 2014 17:45:34 +0000
Message-ID: <CAGAGxbb5xTCQaS7=1BPN0pWPz_Z3MqegJkaJFZfg8Eou+zELYA@mail.gmail.com>
To: Pascal Chevrel <pascal.chevrel@free.fr>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: [PHP6] Function name consistency
From: daverandom@php.net (Chris Wright)

On 23 January 2014 16:50, Pascal Chevrel <pascal.chevrel@free.fr> wrote:
> Maybe it's a stupid idea, you'll tell me :) Wouldn't it be a good thing to
> issue a notice when people use the alias instead of the correct function
> name?
>

This is essentially a description of the visible effects of
deprecation, and would cause a *lot* of issues in userland if this was
done straight away, since there are literally millions of applications
using functions that are candidates to be aliased in every page load -
remember that everything, including error messages, has an overhead.

As Yasuo stated in the first message in the thread:

> We may keep alias 10 or 20 years or even forever.

We can't consider deprecating (or even "soft deprecating" in the
manual, as happened with ext/mysql) any of the old names for a long,
long time, as many of them are far to deeply burned into the PHP
ecosystem.

Thanks, Chris