Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69679 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40843 invoked from network); 18 Oct 2013 13:26:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2013 13:26:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rotorised.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lists@rotorised.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rotorised.com from 117.55.227.19 cause and error) X-PHP-List-Original-Sender: lists@rotorised.com X-Host-Fingerprint: 117.55.227.19 mta19-d1.ip1.cbr1.mail-filtering.com.au Received: from [117.55.227.19] ([117.55.227.19:51105] helo=mta19-d1.ip1.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/43-23638-2F631625 for ; Fri, 18 Oct 2013 09:26:11 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuYBAEk2YVKva64Tl2dsb2JhbABagz++coEkFg4BAQEBAQgWBzyCJQEBBXgBEAsNCwkWDwkDAgECAUUGAQwBBwEBiAHAdY9WB4QpA5k4hHg7g2CKew X-IPAS-Result: AuYBAEk2YVKva64Tl2dsb2JhbABagz++coEkFg4BAQEBAQgWBzyCJQEBBXgBEAsNCwkWDwkDAgECAUUGAQwBBwEBiAHAdY9WB4QpA5k4hHg7g2CKew X-IronPort-AV: E=Sophos;i="4.93,522,1378821600"; d="scan'208";a="847370778" Received: from unknown (HELO ub005lcs09.cbr.the-server.net.au) ([175.107.174.19]) by smtp-data2.ironport1.cbr1.mail-filtering.com.au with ESMTP; 19 Oct 2013 00:26:06 +1100 Received: from 217.33.96.58.static.exetel.com.au ([58.96.33.217]:52343 helo=[192.168.1.237]) by ub005lcs09.cbr.the-server.net.au with esmtpa (Exim 4.80.1) (envelope-from ) id 1VXA45-003zkX-DO; Sat, 19 Oct 2013 00:26:05 +1100 Message-ID: <526136F8.6050300@rotorised.com> Date: Fri, 18 Oct 2013 23:26:16 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Nikita Popov , Rowan Collins CC: PHP Internals References: <525C631E.1050008@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Proposal to deprecate create_function() From: lists@rotorised.com (Ryan McCue) Nikita Popov wrote: > 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). I can say with confidence that if this gets in to PHP, we'll integrate BC support as above (although probably some function name like `_wp_anonymous_function_$i`), and the only real reason we still have this is 5.2 support. I suspect by the time 5.next rolls around, we'll be at least considering dropping 5.2, but that of course depends on usage. At the very least, the plugin ecosystem is starting to look towards dropping 5.2 support, which is where the big issue will be anyway, so that's nice. (FWIW, I always hated the create_function() calls in WordPress anyway.) -- Ryan McCue