Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.176 as permitted sender)
Message-ID: <52602B7A.3080509@gmail.com>
Date: Thu, 17 Oct 2013 19:24:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
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>
In-Reply-To: <CAEZPtU53CH-gGZK7kJnYrPu=VAc0-M-4DUryDBH7TgcEJ=Y6QA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal to deprecate create_function()
From: rowan.collins@gmail.com (Rowan Collins)

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?

If not, it sounds like existing usage is the concern. Which is not to 
belittle the importance of that, I just want to be sure we're coming 
from the same place.

-- 
Rowan Collins
[IMSoP]