Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56542 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14433 invoked from network); 23 Nov 2011 23:23:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2011 23:23:44 -0000 Authentication-Results: pb1.pair.com header.from=mike@rile.ca; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=mike@rile.ca; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rile.ca designates 199.19.173.234 as permitted sender) X-PHP-List-Original-Sender: mike@rile.ca X-Host-Fingerprint: 199.19.173.234 rile.ca Linux 2.6 Received: from [199.19.173.234] ([199.19.173.234:33151] helo=rile.ca) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/21-03584-F708DCE4 for ; Wed, 23 Nov 2011 18:23:44 -0500 Received: from MikePC (s72-38-93-190.static.comm.cgocable.net [72.38.93.190]) (authenticated bits=0) by rile.ca (8.14.4/8.14.4) with ESMTP id pANNNdok003231; Wed, 23 Nov 2011 18:23:39 -0500 To: "'Gustavo Lopes'" , References: <20111123015008.GA12933@panix.com> <20111123023108.GA172@panix.com> <4ECCB549.904@lsces.co.uk> <4ECCBC56.3050602@sugarcrm.com> <20111123141408.GA11940@panix.com> <20111123153100.GB13420@panix.com> <4ECD4231.7070306@sugarcrm.com> In-Reply-To: Date: Wed, 23 Nov 2011 18:23:42 -0500 Message-ID: <000301ccaa36$f0b6ced0$d2246c70$@ca> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcyqL8RFTHBYnlo7QvGcijYQv6D+OgABn+6g Content-Language: en-ca Subject: RE: [PHP-DEV] 5.4 regression: non-existent sub-sub keys now have values From: mike@rile.ca ("Mike Robinson") On November-23-11 5:31 PM Gustavo Lopes wrote: > On Wed, 23 Nov 2011 21:06:09 -0000, Pierre Joye > wrote: > > > The fact that we have reports here showing code not working anymore > > because of this change tells me that it is a BC break. We can call it > > a bug fix but it still breaks code out there for no real benefit but > > edge case usages. We had this situation before, that does not help > us. > > > > I'd say for no benefit at all. Why would anyone ever want to take a > string offset from a string that certainly has length 1? Except for > taking satisfaction in this "improved consistency", I see absolutely no > benefit. > > Up until now, it was deemed a useless but innocuous change. Now that we > found it has pernicious side effects, we ought to revert it. Notwithstanding that this behaviour was possible because of a bug, it has admittedly been relied on since time immemorial, making it a significant BC break. As distasteful as it seems, it absolutely should be reverted IMHO. Best Regards, Mike Robinson