Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69668
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.83.49 as permitted sender)
Message-ID: <52611431.7070407@googlemail.com>
Date: Fri, 18 Oct 2013 12:57:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
CC: internals@lists.php.net
References: <525C631E.1050008@gmail.com> <CAF+90c9z6Xx8GY8zPvg8x0b953oyxfBV=_5znWVX7OG4Rb7oaQ@mail.gmail.com> <52610FFE.7020806@googlemail.com> <327CCB6F-3D5B-410E-84BB-547467E688B1@gmail.com>
In-Reply-To: <327CCB6F-3D5B-410E-84BB-547467E688B1@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal to deprecate create_function()
From: cryptocompress@googlemail.com (Crypto Compress)

Am 18.10.2013 12:51, schrieb Alexey Zakhlestin:
> On 18.10.2013, at 14:39, Crypto Compress <cryptocompress@googlemail.com> wrote:
>
>> Am 18.10.2013 11:26, schrieb Nikita Popov:
>>> You can even replicate the exact
>>> behavior (minus the hiding from get_defined_functions) with just four lines
>>> of code (though I have no idea what you could possibly need this for):
>>>
>>> function create_function($params, $code) {
>>>      static $i = 0;
>>>      $name = "create_function_" . $i++;
>>>      eval("function $name($params) { $code }");
>>>      return $name;
>>> }
>>>
>>> I tried to look on Github what people currently use create_function for,
>>> but with little success. Nearly all results I get are uses in the php
>>> testsuite (copied over to various projects). The only other use case I saw
>>> was in conjunction with the WordPress add_action() function. In this case
>>> the create_function call could always be replaced directly with an
>>> anonymous function (i.e. it didn't need any magic create_function
>>> capabilities).
>> shure all things can be replaced with more and verbose code. What is the benefit of writing all this lines in contrast to one method call?
>> https://github.com/phpcr/phpcr-utils/blob/master/src/PHPCR/Util/Console/Helper/PhpcrCliHelper.php#L111
>>
>> -1 for removing wrappers/abbreviations/and such
>> +1 for bug fixing
>
> I think you misunderstood Nikita's proposal.
> "all these lines" can be put in a library and your code would just continue to work the way it is.
>
> Idea is that it is trivially implemented in userland and there is no much sense to keep it in core.

It is possible to write most of the array functions in plain php with a 
trivial foreach. Can't see the point.