Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69683 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51037 invoked from network); 18 Oct 2013 14:02:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2013 14:02:10 -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:35624] helo=mta19-d1.ip1.cbr1.mail-filtering.com.au) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9B/55-23638-06F31625 for ; Fri, 18 Oct 2013 10:02:09 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuYBAKg+YVKva64Tl2dsb2JhbABagz++coEkFg4BAQEBAQgWBzyCJQEBBXgBEAsNCwkWDwkDAgECAUUGDQEHAQEQh3ENwHeOJ4EvB4QpA5k4hHg7g2CKew X-IPAS-Result: AuYBAKg+YVKva64Tl2dsb2JhbABagz++coEkFg4BAQEBAQgWBzyCJQEBBXgBEAsNCwkWDwkDAgECAUUGDQEHAQEQh3ENwHeOJ4EvB4QpA5k4hHg7g2CKew X-IronPort-AV: E=Sophos;i="4.93,522,1378821600"; d="scan'208";a="847391716" 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 01:02:05 +1100 Received: from 217.33.96.58.static.exetel.com.au ([58.96.33.217]:53779 helo=[192.168.1.237]) by ub005lcs09.cbr.the-server.net.au with esmtpa (Exim 4.80.1) (envelope-from ) id 1VXAcp-0044Ty-NX; Sat, 19 Oct 2013 01:02:00 +1100 Message-ID: <52613F62.6090407@rotorised.com> Date: Sat, 19 Oct 2013 00:02:10 +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: Rowan Collins CC: PHP Internals References: <525C631E.1050008@gmail.com> <526136F8.6050300@rotorised.com> <52613DCD.2010301@gmail.com> In-Reply-To: <52613DCD.2010301@gmail.com> 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) Rowan Collins wrote: > That's interesting to hear - I have no knowledge of the Wordpress > community and decision-making apparatus, so wasn't sure what the > reaction would be. While digging around for references, I did find this > ticket about removing a lot of the create_functions from core: > http://core.trac.wordpress.org/ticket/14424 For context, one of the big uses was returning static values, like true/false/etc. We now have __return_false()/__return_empty_array()/etc for those uses. We also discourage it from being used for callbacks, as the runtime-generated-naming means it's impossible to later remove it without a variable reference to the name (ditto for closures, but people typically only use those in development, not production). There's only one place I can think of in the plugin community where it's still used a fair bit (widget registration), but we can work on discouraging that and there's a fair amount of time until the next release in any case. Personal +1 on this. -- Ryan McCue