Re: [RFC][VOTE] E_WARNING on invalid container read-adccess
| From: | Christoph M. Becker | Date: | Thu, 25 Aug 2016 11:49:51 +0000 |
| Subject: | Re: [RFC][VOTE] E_WARNING on invalid container read-adccess | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95444@lists.php.net to get a copy of this message | ||
On 16.08.2016 at 17:55, David Walker wrote:
> I raised this concept a couple weeks ago to a couple +1's. Discussion was
> held mostly upon the PR [1], and I went through and documented within the
> RFC [2]. I'd like to go ahead and open up the RFC to voting to the scope
> that it is written.
>
> [1] https://github.com/php/php-src/pull/2031
> [2]
> https://wiki.php.net/rfc/notice-for-non-valid-array-container
For the record, the RFC rightly claims:
| The default behavior, of a silent NULL return, is not correctly
| defined in the Array Documentation however is noted in a comment
I have documented this behavior now[3], and removed the note, which was
not quite correct, because it claimed that TRUE would be returned when
array dereferencing NULL, bool or int.
[3] <http://svn.php.net/viewvc?view=revision&revision=339937>
--
Christoph M. Becker