Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92224
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender)
To: Marco Pivetta <ocramius@gmail.com>,
 PHP Internals List <internals@lists.php.net>
References: <CADyq6sLu4npQ1Q2wE7JZ5Pgev71ZWmU+CoTumG_VVvNGToc2ow@mail.gmail.com>
Message-ID: <570CF4E4.6070800@gmx.de>
Date: Tue, 12 Apr 2016 15:15:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CADyq6sLu4npQ1Q2wE7JZ5Pgev71ZWmU+CoTumG_VVvNGToc2ow@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Array key access on non-array values - to be made illegal?
From: cmbecker69@gmx.de (Christoph Becker)

On 12.04.2016 at 14:59, Marco Pivetta wrote:

> I just stumbled upon behavior that seems to "fail silently" regardless of
> its very questionable validity:
> 
> <?php
> 
> $a = 1;
> 
> var_dump($a[123]); // NULL, no notice
> 
> https://3v4l.org/b3rDr
> 
> Are there specific reasons why no notice is thrown? Is it by design? If so,
> does anyone remember why?
> 
> I haven't checked if this affects other types too. I know that an
> assignment to an array key of a non-array would cause a cast of the value
> to `array`, but a mere read operation should surely cause a notice to be
> raised in the above scenario.

For the record: there are several bug reports/feature requests regarding
this issue, e.g. <https://bugs.php.net/bug.php?id=37676>.

-- 
Christoph M. Becker