Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95513
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.163 cause and error)
MIME-Version: 1.0
References: <CADVQu1QXag1h_hnOcFYejMbsDrV+4ZQCwKNJmb4EedBB6S33Ww@mail.gmail.com>
 <1e6cac8a-e1af-c9e7-a900-a2efda0771dd@gmx.de> <BY2PR0201MB17843B394401BED590828E3ABFE30@BY2PR0201MB1784.namprd02.prod.outlook.com>
In-Reply-To: <BY2PR0201MB17843B394401BED590828E3ABFE30@BY2PR0201MB1784.namprd02.prod.outlook.com>
Date: Wed, 31 Aug 2016 07:58:16 +0000
Message-ID: <CANUQDChTD17kqGe+621wkEzaq-WZoSZH7MTSwP-9EVLqRmhvcg@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>, "Christoph M. Becker" <cmbecker69@gmx.de>, David Walker <dave@mudsite.com>, 
	PHP internals <internals@lists.php.net>
Cc: Nikita Popov <nikic@php.net>
Content-Type: multipart/alternative; boundary=001a11438e165baacd053b597642
Subject: Re: [PHP-DEV] Re: [RFC][VOTE] E_WARNING on invalid container read-adccess
From: me@kelunik.com (Niklas Keller)

--001a11438e165baacd053b597642
Content-Type: text/plain; charset=UTF-8

Dmitry Stogov <dmitry@zend.com> schrieb am Mi., 31. Aug. 2016, 08:37:

> I vote NO, because the implementation introduces more problems than
> intents to fix.
>
> For example the following code starts to throw exception:
>
>
> <?php $a = [null]; $c = null; var_dump($a[0][0] + $c[0]); ?>
>

Array access on null should always throw IMO.

BTW, I'm not against the feature, I'm against the implementation.
>
> It's just can't be committed in current state.


I think we vote on features, not implementations. Therefore you should
probably have voted yes.

Thanks. Dmitry.
>
>
> ________________________________
> From: Christoph M. Becker <cmbecker69@gmx.de>
> Sent: Thursday, August 25, 2016 2:49:51 PM
> To: David Walker; PHP internals
> Subject: [PHP-DEV] Re: [RFC][VOTE] E_WARNING on invalid container
> read-adccess
>
> 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
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a11438e165baacd053b597642--