Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69657
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <52602B7A.3080509@gmail.com>
References: <525C631E.1050008@gmail.com>
	<1381853515.3980.195.camel@guybrush>
	<526002B4.9010808@gmail.com>
	<CAEZPtU7iJwwaY8xVb5a9emwKx0Bie_Xu2F_2AuYU-ijtGiGfZA@mail.gmail.com>
	<526022E1.1040406@gmail.com>
	<CAEZPtU53CH-gGZK7kJnYrPu=VAc0-M-4DUryDBH7TgcEJ=Y6QA@mail.gmail.com>
	<52602B7A.3080509@gmail.com>
Date: Thu, 17 Oct 2013 12:29:25 -0700
Message-ID: <CAEZPtU7_0oY1Ya=df20-R3Fhz1XFfoUC3vrY7i4yJi+ZU8_oyw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Proposal to deprecate create_function()
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Oct 17, 2013 at 11:24 AM, Rowan Collins <rowan.collins@gmail.com> wrote:
> On 17/10/2013 18:52, Pierre Joye wrote:
>>>
>>> The only real difference I can see with create_function is that it is/was
>>> >more widely used; is that your concern, or do you see a fundamental
>>> >difference between the two situations?
>>
>> I do. create_function is used for many very valid use cases, safely,
>> much more than /e ever was (and its security impact was much bigger).
>> Deprecating it does not help us nor our users at this stage.
>
>
> If create_function did not exist, would any of those use cases persuade you
> that it should?

Not with latest PHP releases, but that's the point: we try to keep BC.



-- 
Pierre

@pierrejoye | http://www.libgd.org