Re: [RFC][Post-Discussion]: E_WARNING when using array-index on non valid container
| From: | lists@rhsoft.net | Date: | Wed, 31 May 2017 16:21:59 +0000 |
| Subject: | Re: [RFC][Post-Discussion]: E_WARNING when using array-index on non valid container | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99301@lists.php.net to get a copy of this message | ||
Am 31.05.2017 um 18:16 schrieb Dan Ackroyd:
On 11 January 2017 at 15:42, David Walker <dave@mudsite.com> wrote:because otherwise you couldn't do something like below with a 1-liner and so that PHP5.4 feature becomes pretty useless because for a isset() you need to store it in a var function GetKatMaxSort(): int { global $db; return (int)$db->fetch_row($db->query('select max(hsort) from ' . sql_prefix . 'haupt', 1, 0))[0]; }Joe had requested renewed discussion on the accepted RFC[1] and my proposed PR[2] be brought forward again for implementation discussion, and to come up with a resolution. Any thoughts on a better implementation, or other use cases that need attention would be appreciated.Please could you give us an update on the status of the implementation, and are you still looking for advice on how what would be needed to complete it? ps for the record, I just spent an hour today trying to figure out why code equivalent to $foo = null; echo $foo['bar'] wasn't triggering an error, so I hope this can make it for 7.2