Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85384 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84039 invoked from network); 21 Mar 2015 18:30:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Mar 2015 18:30:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=dev@mabe.berlin; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=dev@mabe.berlin; sender-id=unknown Received-SPF: error (pb1.pair.com: domain mabe.berlin from 80.237.132.167 cause and error) X-PHP-List-Original-Sender: dev@mabe.berlin X-Host-Fingerprint: 80.237.132.167 wp160.webpack.hosteurope.de Received: from [80.237.132.167] ([80.237.132.167:45782] helo=wp160.webpack.hosteurope.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/DB-18917-7C8BD055 for ; Sat, 21 Mar 2015 13:30:32 -0500 Received: from dslb-178-008-196-184.178.008.pools.vodafone-ip.de ([178.8.196.184] helo=[192.168.178.30]); authenticated by wp160.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1YZOAF-0000Bz-R5; Sat, 21 Mar 2015 19:30:27 +0100 Message-ID: <550DB8C3.6020800@mabe.berlin> Date: Sat, 21 Mar 2015 19:30:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <60525DAED8264509BF14D25637CD7C1E@gmail.com> <4DBD500BD91A4CCCBFDDFD5DD80FEC74@gmail.com> <20150320115351.GE10567@phcomp.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;dev@mabe.berlin;1426962632;663e676a; Subject: Re: [PHP-DEV] =?UTF-8?B?5Zue5aSN77yaIFtSRkNdW0RJU0NVU1NJT05dIEFk?= =?UTF-8?B?ZCBwcmVnX3JlcGxhY2VfY2FsbGJhY2tfYXJyYXkgZnVuY3Rpb24=?= From: dev@mabe.berlin (Marc Bennewitz) I also had a question! Didn't you noticed it? Am 20.03.2015 um 16:49 schrieb Marc Bennewitz: > Why not simply allow the callback to be an array, too? Marc Am 21.03.2015 um 09:14 schrieb Xinchen Hui: > Hey: > > On Fri, Mar 20, 2015 at 9:14 PM, Xinchen Hui wrote: >> Hey: >> >> On Fri, Mar 20, 2015 at 7:53 PM, Alain Williams wrote: >>> On Fri, Mar 20, 2015 at 10:46:58PM +1100, Pierre Joye wrote: >>>> On Fri, Mar 20, 2015 at 7:03 PM, Wei Dai wrote: >>>>> Hi internals, >>>>>> Hi internals, >>>>>> >>>>>> The RFC to add a user-land function for an easy-to-use and reliable >>>>>> preg_replace_callback_array() in PHP is up for discussion: >>>>>> https://wiki.php.net/rfc/preg_replace_callback_array >>>>>> >>>>>> This proposes adding one function: `preg_replace_callback_array()` that >>>>>> is the better way to Implement when there are multiple patterns need to >>>>>> replace. >>>>>> >>>>>> I would love to hear your feedback! :) >>>>>> Any objections? >>>>> I’ve sent this mail for four days, I don’t know if this RFC needs a vote. >>>>> If you guys have no objections on this, please review the code and merge it, >>>>> thanks. >>>> Nice job, i like the idea. >>>> >>>> I am not sure about a RFC or not. It somehow looks like a sane >>>> replacement for something we killed (with good reasons). >>>> >>>> Let see what the other think :) >>> I used s/something/code/ge in a perl script that I wrote a few days ago. Very >>> useful. It would have been a lot more work to do it another way. >>> >>> So: +1 to the ability to do this, regardless of what mechanism is eventually chosen. >> I also +1 for this. >> >> if there is no objections raises, I am going to merge it tomorrow.. > merged > > thanks >> thanks >>> -- >>> Alain Williams >>> Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. >>> +44 (0) 787 668 0256 http://www.phcomp.co.uk/ >>> Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php >>> #include >>> >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >> >> >> -- >> Xinchen Hui >> @Laruence >> http://www.laruence.com/ > >