Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56556
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.132 cause and error)
Message-ID: <4ECE0F47.1040504@lsces.co.uk>
Date: Thu, 24 Nov 2011 09:32:55 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Firefox/7.0.1 SeaMonkey/2.4.1
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <20111123015008.GA12933@panix.com> <CACQesk6UuGUgyJz3hsGVE0crJx3GCkjTTpLb4xNGTm1goLzO8Q@mail.gmail.com> <20111123023108.GA172@panix.com> <CACQesk5kj=4kzvTDiLL1oOLBXZrn4WdUcLXdbyMLTa=OdhGTcw@mail.gmail.com> <4ECCB549.904@lsces.co.uk> <4ECCBC56.3050602@sugarcrm.com> <20111123141408.GA11940@panix.com> <4ECD40E2.1000601@sugarcrm.com> <CAH-PCH6f30p6AfNT9z=wVPURo4ko08sMTwHiEQsdpauN-cYtwQ@mail.gmail.com> <4ECD48AD.1020207@sugarcrm.com> <4ECD91F4.5040303@gmail.com> <CAH-PCH7GCDOdnHve-mNdkPYbBN+WGLJN2BP8pdpXmVz=0FQ0mg@mail.gmail.com> <4ECDAEE5.7020205@gmail.com> <4ECE0887.3030109@lsces.co.uk> <4ECE0AC3.1050405@sugarcrm.com>
In-Reply-To: <4ECE0AC3.1050405@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 5.4 regression: non-existent sub-sub keys now have
 values
From: lester@lsces.co.uk (Lester Caine)

Stas Malyshev wrote:
> Hi!
>
>> That would help a lot ... this is not a problem of "so the developer can fix his
>> code" but rather so we can fix legacy code which other non-developers are
>> currently using happily ... If *I* had written the code I would not have done it
>> the way it is currently structured, but I'm not about to spend time
>> re-engineering it ... I just want to plug the holes quickly so it continues to
>> work.
>
> OK, notice is probably technically feasible, though I still not like the idea
> too much. When you want to produce this notice? Producing it on any string would
> probably break code like $a['1'] which has it's legitimate uses and I'm sure can
> be seen around. Should be produce notice if the string has non-numeric chars?
> That's slow down this operation a little, though probably not critically as
> conversion is going to scan the string anyway.

The 'index not found' error usually pops up where I'm messing up the existing 
'logic' so something that flags that a 'phantom' index has been created when a 
'real' ['sub-element'] was being looked for. In my own case I'm sure once I dig 
out the problem the answer will be obvious as well, but I simply don't have the 
time to spend. So currently a production 5.4 upgrade is not possible.

It would be useful if some of the other people flagging this problem could 
provide some info on what is failing ... the original PEAR problem for example? 
I'm not sure that any of us know just what edge case is causing a hickup?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php