Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100962
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)
To: Filippo Tessarotto <zoeslam@gmail.com>, internals@lists.php.net
References: <7639e065-451b-0f2e-1985-5e3d31ec1b68@gmail.com>
Message-ID: <363025d5-bd57-01e6-0fba-0120050cd4dc@gmx.de>
Date: Fri, 27 Oct 2017 13:47:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <7639e065-451b-0f2e-1985-5e3d31ec1b68@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: Raise E_NOTICE for null castings
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 27.10.2017 at 11:49, Filippo Tessarotto wrote:

> Hi, I would like to propose an RFC to raise an E_NOTICE when a variable
> "initialized" to null is casted to other types:
> 
> $foo = null;
> var_dump($foo['bar']);
> var_dump($foo . 'bar');
> var_dump($foo + 2);
> var_dump($foo & 2);
> // At the time being, this code produces no errors
> 
> The eventual vote may be split one for each case.
> 
> What do you think?

Note that there is already an accepted RFC regarding rasing E_WARNING
for invalid container read array-access[1].  However, it has not been
implemented yet, due to difficulties, see the discussion on PR #2031[2].

[1] <https://wiki.php.net/rfc/notice-for-non-valid-array-container>
[2] <https://github.com/php/php-src/pull/2031>

-- 
Christoph M. Becker