Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111848
Date: Sat, 05 Sep 2020 21:44:01 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <c3fdbfe3cadde9af0e217e6880f3894e345751e28138584e698727e84590b292@mahalux.com>
References: <c3fdbfe3cadde9af0e217e6880f3894e345751e28138584e698727e84590b292@mahalux.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----WKI6TIN6OWNH3L42H9XS4IVGMVW11P"
Content-Transfer-Encoding: 7bit
To: internals@lists.php.net
Message-ID: <541FC73F-CC0C-413F-ACD4-08A8EDF1E1C1@gmail.com>
Subject: Re: [PHP-DEV] __isset() and null value
From: rowan.collins@gmail.com (Rowan Tommins)

------WKI6TIN6OWNH3L42H9XS4IVGMVW11P
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Michael,

On 4 September 2020 18:03:29 BST, "Michael Vo=C5=99=C3=AD=C5=A1ek - =C4=8C=
VUT FEL" <vorismi3@fel=2Ecvut=2Ecz> wrote:
>Ideally, we should introduce __exist() which should return true even if
>value is null

Magic methods in PHP allow the user to overload some built-in operator or =
behaviour, so it doesn't make sense to talk about a new magic method in ter=
ms of how users are expected to implement it without first describing what =
built-in functionality it overloads=2E

Is the idea that $foo->__exists($bar) would be called when running propert=
y_exists($foo, $bar)?

If so I suspect most cases would be clearer if they used some context-spec=
ific interface with a well-named method=2E For instance:

interface SomeORM\DynamicDBModel {
    public function hasColumn($columnName): bool;
}

A notable difference from __isset is that you can write isset($foo->bar) w=
ithout having 'bar' as a string value, which AFAIK is not possible with "ex=
ists"=2E

Regards,
--=20
Rowan Tommins
[IMSoP]
------WKI6TIN6OWNH3L42H9XS4IVGMVW11P--