Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112168
MIME-Version: 1.0
References: <CAM0CcxjF3TzcFZegM3KvA07K_dQPnN=Mp-kkYK94Mja487KKtQ@mail.gmail.com>
 <CAG9XoMQrp_SvoZ2Ls+=ybTeZYxDbyASda2wFu=zGKkFSwJ3yPw@mail.gmail.com>
 <CAFPFaM+8rSM4Meisr8Nwxu5DdA5=D+D7r2n6ptN4_W8hV3X9_Q@mail.gmail.com>
 <CAM0Ccxii9WdUndo_2-NTB7Z-QD0dwn_7egyMLtkHXG2Ffn2HKg@mail.gmail.com> <CAFPFaMKGct7Ec7MvfYjTBwP2m7WWAGyEVaEXJteOwKcsECz0Hw@mail.gmail.com>
In-Reply-To: <CAFPFaMKGct7Ec7MvfYjTBwP2m7WWAGyEVaEXJteOwKcsECz0Hw@mail.gmail.com>
Date: Tue, 3 Nov 2020 21:19:42 +0200
Message-ID: <CAM0CcxjWxsFnZ6++MPcX-u3iYUx-4ghPsdk6GvMs98hJNN9g8g@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000092efb905b338bfc5"
Subject: Fwd: [PHP-DEV] Nullsafe
From: zsidelnik@gmail.com (Eugene Sidelnyk)

--00000000000092efb905b338bfc5
Content-Type: text/plain; charset="UTF-8"

---------- Forwarded message ---------
From: G. P. B. <george.banyard@gmail.com>
Date: Tue, Nov 3, 2020 at 9:08 PM
Subject: Re: [PHP-DEV] Nullsafe
To: Eugene Sidelnyk <zsidelnik@gmail.com>


On Tue, 3 Nov 2020 at 19:05, Eugene Sidelnyk <zsidelnik@gmail.com> wrote:

> Null value by itself was invented to indicate lack of data.
> But we can't just use it instead of objects, because of how it works.
> We need to create a boilerplate of NullObjects.
> Consider the abstract factory example:
> https://3v4l.org/9D9LU
>
> The problem is not with nullsafe operator. It is basically in null
> constant. To correctly work with absence of object, NullObjects is required
> (one for each abstraction).
>
> > I don't see why users should return null values more often.
>
> They should not return null values! But with nullsafe they will be prone
> to.
>
>
First of all please bottom post instead of top posting.

Secondly, that's just your philosophy and the null safe operator was
introduced to
accommodate this way of thinking.
However, this does not mean it's better or should be the way it works,
especially now
that the null safe operator has already been implemented, and changed
established
semantics need a *good* reason.

Regards,

George P. Banyard

--00000000000092efb905b338bfc5--