Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90634 invoked from network); 10 Jan 2015 21:32:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jan 2015 21:32:16 -0000 Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:3673] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/45-48183-F5A91B45 for ; Sat, 10 Jan 2015 16:32:16 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 197194B008E; Sat, 10 Jan 2015 22:30:07 +0100 (CET) Reply-To: To: "'christopher jones'" , References: <003e01d0290b$2387dd30$6a979790$@yahoo.fr> <007801d02ba0$659b9080$30d2b180$@tekwire.net> <000901d02cf7$5adb7360$10925a20$@tekwire.net> <54B18F2E.702@oracle.com> In-Reply-To: <54B18F2E.702@oracle.com> Date: Sat, 10 Jan 2015 22:32:05 +0100 Message-ID: <000e01d02d1c$e1c71800$a5554800$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJLUGZm//Pi9sQwKU1Klfwo9ikS+QIf8jOCAeK3NVEB2wmVxwKFWfjDm4B0z7A= Content-Language: fr X-Antivirus: avast! (VPS 150110-2, 10/01/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] [BugFest] Feature request #38685: str_[i]replace(): Add support for (string needle, array replace) From: francois@tekwire.net (=?UTF-8?Q?Fran=C3=A7ois_Laupretre?=) > De : christopher jones [mailto:christopher.jones@oracle.com] > >> To summarize, I started with a rather simple feature request and was >> then pushed by external wishes. > > See #13 at > https://blogs.oracle.com/opal/entry/the_mysterious_php_rfc_process > "Take advice on board but make sure your feature doesn't end up being > designed by a committee." I appreciate, really. I see that I was not clear enough when I said that I was 'pushed by = external wishes'. I must reassure you as I am generally well-known to = be quite 'unpushable' when the advices I receive don't fit my = objectives. The whole challenge, here, as anybody (should) know, is to = avoid denaturing your vision, while keeping an open mind and accepting = advices and constructive critics. When people are constructive and know = what they are talking about, negotiating a proper mix is generally easy. = When it is not the case, it is harder... but we are just weak humans = and, sometimes, battles of egos are also part of the game... These last 25 years (yes, I am probably MUCH older than everyone else = here but that's not a reason to throw stones at me :), I have = continuously opposed weak committee decisions and I am quite experienced = (although tired) on this kind of process. This is also the reason why I = didn't have only friends on the PHP internals ML, but that's all over = now... To illustrate this, I just modified the RFC to indicate that the trend = was to limit search recursion to 1 level, as I also think that, even if = attractive from a theoretical point of view, nested search would be too = confusing for a marginal benefit. On the other side, I still insist on = arbitrarily-nested subject because I think it is worth the = (all-relative) added complexity. I am waiting for your comments on the RFC. PS: The only persistent fault I recognize is writing too long messages = :) Regards Fran=C3=A7ois