Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56575
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
Reply-To: RQuadling@GMail.com
In-Reply-To: <20111123015008.GA12933@panix.com>
References: <20111123015008.GA12933@panix.com>
Date: Thu, 24 Nov 2011 12:33:14 +0000
Message-ID: <CAKUjMCWpv98-+VfxkSEjCgRDXJ5KXZaGCEA=0Q=h0kvXEtuGHg@mail.gmail.com>
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.4 regression: non-existent sub-sub keys now have values
From: rquadling@gmail.com (Richard Quadling)

On 23 November 2011 01:50, Daniel Convissor
<danielc@analysisandsolutions.com> wrote:
> Hi Folks:
>
> I just stumbled upon a regression in 5.4. =C2=A0In an array, a sub-sub-ke=
y of
> an existing key is now returning a letter of the value indexed by the
> main key. =C2=A0I'm raising it here so it doesn't get lost.
>
> https://bugs.php.net/bug.php?id=3D60362
>
> Thanks,
>
> --Dan

I've just ran the code for the bug through all the V5 releases/betas/alphas=
/RCs.

V5.0.0 to V5.0.2

BEHAVIOR CHANGED: sub-key 'non_existent' is not set.
expected: sub-key 1 is set: string(1) "o"
-------------------
good: sub-sub-key 'sub_sub' is not set.
good: sub-sub-key 0 is not set.
-------------------
BEHAVIOR CHANGED: sub-key 'non_existent' is empty.
expected: sub-key 1 is NOT empty: string(1) "o"
-------------------
good: sub-sub-key 'sub_sub' is empty.
good: sub-sub-key 0 is empty.



V5.0.3 (don't have)



V5.0.4 to V5.3.9RC2-dev (as at around 10am GMT on the 23rd Nov 2011).
expected: sub-key 'non_existent' is set: string(1) "f"
expected: sub-key 1 is set: string(1) "o"
-------------------
good: sub-sub-key 'sub_sub' is not set.
good: sub-sub-key 0 is not set.
-------------------
expected: sub-key 'non_existent' is not empty: string(1) "f"
expected: sub-key 1 is NOT empty: string(1) "o"
-------------------
good: sub-sub-key 'sub_sub' is empty.
good: sub-sub-key 0 is empty.



V5.4+ (betas and RCs)
expected: sub-key 'non_existent' is set: string(1) "f"
expected: sub-key 1 is set: string(1) "o"
-------------------
BEHAVIOR CHANGED: sub-key 'sub_sub' is set: string(1) "f"
BEHAVIOR CHANGED: sub-sub-key 0 is set: string(1) "o"
-------------------
expected: sub-key 'non_existent' is not empty: string(1) "f"
expected: sub-key 1 is NOT empty: string(1) "o"
-------------------
BEHAVIOR CHANGED: sub-sub-key 'sub_sub' is not empty: string(1) "f"
BEHAVIOR CHANGED: sub-sub-key 0 is not empty: string(1) "o"



So there was a previous bug fix in V5.0.2 (maybe 5.0.3).

So, the whole type juggling point here is mute. It has been that way
for a very long time. I just didn't realise it.

And if that is a valid result
(var_dump($arr['exists']['non_existent']) =3D=3D=3D 'f') - which it now is
obviously is, then the change in V5.4 is certainly a bug fix.

But, it is a significant enough issue that warrants a decent amount of
documentation.



--=20
Richard Quadling
Twitter : EE : Zend : PHPDoc : Fantasy Shopper
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea=C2=A0:
fan.sh/6/370