Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69568
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <525C631E.1050008@gmail.com>
References: <525C631E.1050008@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 15 Oct 2013 18:11:55 +0200
Message-ID: <1381853515.3980.195.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal to deprecate create_function()
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2013-10-14 at 22:33 +0100, Rowan Collins wrote:
> I would like to propose that create_function() be officially deprecated, 
> to encourage people to use the much safer and more powerful anonymous 
> functions we've had since 5.3, and eventually allow this relic to be 
> removed from the language.

In general: Getting rid of it is good. But mind that closures are no
full replacement as with create_function() the code can be created on
the fly. Emulating it with eval() is also complicated as it has this
nice trick of creating function names which start with \0 and therefore
don't appear in function lists.

I don't think this is a commonly used feature, but when kicking
create_function() we should not call closures+eval a full replacement.

johannes