Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86578
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender)
Message-ID: <5578BC5F.2010305@gmx.de>
Date: Thu, 11 Jun 2015 00:38:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Yasuo Ohgaki <yohgaki@ohgaki.net>, 
 Nikita Popov <nikita.ppv@gmail.com>
CC: Stanislav Malyshev <smalyshev@gmail.com>, 
 Matt Wilmas <php_lists@realplain.com>,
 internals@lists.php.net
References: <5576051A.3040800@gmx.de> <55760771.6020802@gmail.com> <CAGa2bXaknp0sNwk0JqfUPhURToazTfS40cy9ycY09XJT7AeaCw@mail.gmail.com> <778F345F9918474AB8CAAB03082ECBF7@pc1> <CAGa2bXZQb3UooF+cZJ9jKv0uVLFZSgcN=xoE6mYLG8UDZqc_Qg@mail.gmail.com> <5577DEE4.8030205@gmail.com> <CAF+90c_1s+qGd9UwOMK7OutRw8M0SZzsseQXa_53z0nh0s_Fxw@mail.gmail.com> <CAGa2bXbi3DCj6YwoLxDxe2+7mjShHgm1jqqP=ABcVUHiQqErxw@mail.gmail.com>
In-Reply-To: <CAGa2bXbi3DCj6YwoLxDxe2+7mjShHgm1jqqP=ABcVUHiQqErxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Array dereferencing of scalars
From: cmbecker69@gmx.de (Christoph Becker)

Yasuo Ohgaki wrote:

> On Wed, Jun 10, 2015 at 5:30 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> 
>> On Wed, Jun 10, 2015 at 8:53 AM, Stanislav Malyshev <smalyshev@gmail.com>
>> wrote:
>>
>>>>  <?php
>>>>  $foo = 42;
>>>>  $foo['bar']; // => NULL
>>>>  $v = NULL;
>>>>  $v[0][1][2][3][4][5][6][7][8][9]; // NULL
>>>>
>>>> this code is semantically wrong and I would like to have error/exception
>>>> for such
>>>> erroneous codes. It's inconsistent with array object, too.
>>>
>>> Why it's wrong? You try to get that's something not there, you get NULL.
>>> I don't see anything wrong. Adding fatal error about every little thing
>>> that isn't as expected never was how PHP worked.
>>
>> I agree with what other people have said here: We should keep the behavior
>> for NULL, but drop the nonsense for other types - (42)[24] not throwing a
>> notice is quite ridiculous, that seems like a pretty obvious bug to me.
> 
> I agree that NULL is debatable. In PHP, NULL is treated as 0/false by its
> context.
> It's simpler if we get rid of the behavior altogether. IMO.
> 
> Anyway, removing undefined behavior from other types may be good enough so
> I don't insist.

+1

-- 
Christoph M. Becker