Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80197 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64282 invoked from network); 5 Jan 2015 20:28:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2015 20:28:21 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.51 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.51 mail-pa0-f51.google.com Received: from [209.85.220.51] ([209.85.220.51:49589] helo=mail-pa0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CF/48-21693-4E3FAA45 for ; Mon, 05 Jan 2015 15:28:20 -0500 Received: by mail-pa0-f51.google.com with SMTP id ey11so29553580pad.10 for ; Mon, 05 Jan 2015 12:28:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UrHE6dphQBeAB2Eyk+CD7ZgqXK0yzAakDASn2x1eSzI=; b=uVIWvTS5gGN9tIZN06sjAFcI0r2aJ+qxeaGXpupWVMmXWUxSIT1nxdbncZEAzzX0Wm B8e3nylXcBQN8/WjZe6C7XbzjF1tnW4HHlYSBQkGQU37IBzO0hu2Ooi+SqlHFHoIasyr kq/Pw6PLB08ZqcLajWUxW2qt4aOssGS0UpcPRGB1mL9NneSGPcvilR68R5I1mH/R0bey 6K0g6WIKM8n9gdt9WL3L5Xm5N1huZYyK7ONYowd6YwW9hg07RMhIG1VdXquCn7DNrqtu FXt2CwEUni+M2NaYg+8ufkSiHNpX1zExutlLSE2oCzMgFAwnILP0eCi6B3P3EXQO0PHJ SGCQ== X-Received: by 10.68.180.130 with SMTP id do2mr78015014pbc.54.1420489697303; Mon, 05 Jan 2015 12:28:17 -0800 (PST) Received: from stas-air.corp.wikimedia.org (tan4.corp.wikimedia.org. [198.73.209.4]) by mx.google.com with ESMTPSA id vl1sm54958080pbc.62.2015.01.05.12.28.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Jan 2015 12:28:16 -0800 (PST) Message-ID: <54AAF3DE.2050508@gmail.com> Date: Mon, 05 Jan 2015 12:28:14 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Ferenc Kovacs , Andrea Faulds CC: nf.laupretre@yahoo.fr, PHP Internals References: <003e01d0290b$2387dd30$6a979790$@yahoo.fr> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [BugFest] Feature request #38685: str_[i]replace(): Add support for (string needle, array replace) From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > usually each BC break would warrant an RFC and a vote, but I'm not sure > many people would use str_replace("foo", array("bar"), $subject); and > expect the implicit array to string conversion of array("bar") => "Array" > which also emits a notice. > let's see what others think. I wouldn't consider this a BC break. Anybody who relies on implicit array->string conversion has a bug anyway, and we allow that implicit conversion to survive only for legacy reasons, but I don't think it should drag behind itself the promise we'd never support array parameter where there was only string before. In summary, I'd say no BC break here. -- Stas Malyshev smalyshev@gmail.com