Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100724
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain me.com designates 17.142.194.252 as permitted sender)
Date: Wed, 20 Sep 2017 19:23:23 +0200
To: internals@lists.php.net, "=?utf-8?Q?lists=40rhsoft.net?=" <lists@rhsoft.net>
Message-ID: <75c3c518-56db-4887-99c7-32685e6e5f76@Spark>
In-reply-to: <a24620a6-04a7-8b61-2ac6-11d63d77e9a9@rhsoft.net>
References: <0040eda1-f2d4-408e-a3e1-fe3daf756dfd@Spark>
 <a24620a6-04a7-8b61-2ac6-11d63d77e9a9@rhsoft.net>
MIME-version: 1.0
Content-type: multipart/alternative; boundary=59c2a480_643c9869_aedc
Subject: Re: [PHP-DEV] [RFC] Consistent null behaviour
From: ilija.tovilo@me.com

--59c2a480_643c9869_aedc
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I realized after sending the initial E-Mail that there might be more brea=
king changes than I thought, like the one you suggested.

The same thing actually happens for bools, ints and floats:
https://3v4l.org/jvVbO

I wouldn=E2=80=99t depend on this behaviour since you=E2=80=99d get error=
s depending on what is returned, like an empty array, a string, an object=
 or resource.

Regards


On 20 Sep 2017, 19:18 +0200, lists=40rhsoft.net <lists=40rhsoft.net>, wro=
te:
>
>
> Am 20.09.2017 um 19:06 schrieb ilija.tovilo=40me.com:
> > Hi everybody=21
> >
> > To my surprise, I noticed today that an array access on a =60null=60 =
value returns =60null=60 without any warning whatsoever.
> > Accessing the property of a =60null=60 value gives you a notice, whil=
e calling a function on that =60null=60 value gives you a fatal error.
> >
> > https://3v4l.org/ZSZHN
> >
> > This is pretty inconsistent. IMO all of these should be fatal errors,=
 although I realize that might be a bit drastic for PHP 8.
> > We should at least give the user a notice when using array access on =
a =60null=60 value.
> >
> > Any thoughts=3F
> wouldn't that break code like below which is IMHO the best usecase of
> the PHP 5.6 feature that you can directly access a array field of a
> function result and the type-casting encsues that the return-type is
> always int
>
> function GetSKatMaxSort(int =24archive=3D0): int
> =7B
> return (int)mysqli=5Ffetch=5Frow(=24this->db->query(=22select SQL=5FNO=5F=
CACHE
> max(ssort) from =7B=24this->db->table=7D where sarchive=3D=24archive=22=
, 1))=5B0=5D;
> =7D
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--59c2a480_643c9869_aedc--