Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112162 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 24805 invoked from network); 3 Nov 2020 19:49:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Nov 2020 19:49:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0900F1804B5 for ; Tue, 3 Nov 2020 11:09:55 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [209.85.218.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 3 Nov 2020 11:09:54 -0800 (PST) Received: by mail-ej1-f48.google.com with SMTP id dk16so25244180ejb.12 for ; Tue, 03 Nov 2020 11:09:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=kr9OscMm04PrOpoWV8qOgACMs72SLt4m+tWnRpecsH8=; b=EL2Fx0gGcUOKfTvkAepQg4AceOAxrj/J0wHfipurFM/491lVA9DE/JP6ANpMQvIYiA lGEBqGxVSg22I1bJhad5reAa3BqKtjH705X87QXxWZOesF0upVMLbMIHuZsuFN2GDtD9 YJmaHwE+qdkWOuro0Y8QxlAzVyt1EtzQqTMduKbq+FeE3IC3ucbL1ummo6b/RUrAeVIi rJ3fp2qm0De545uRSne+x2ik5Or1jB0dt9eErgxCC5qFFXHlbjx2nAxAv2iIHwZ5AKOf 4td4r2xFrNIuvKmmEmpWE5VZ3J/GeH53vHvI9uOldVIdcIg0/8U30UjlpeZdY1oKBT3c 6LCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kr9OscMm04PrOpoWV8qOgACMs72SLt4m+tWnRpecsH8=; b=l3Kol92bN5mDcrxJuSdIHWW1JwewwjwcXWfr561o4lPvO9d1sv95u/X7jLXTciS8I6 tNVcsTOuDEQg0GD8+IY6ELlkfRx9UgA9RvOZrAodNy5EWFwZ2BPRjr5YFyvp5XO9hgy7 QERt3Jv57SsbD2TDnnFRMO5K7FSqbKdAZQF9iamLXdBzD8KgdpH/zXL3dvra/c2hexny 3a3MTbs1Xt4uqoqRD1K7oJKTOtaX/jc6eIQvf1YkdGfFCprvWUyURVNBE0cndIV/m2y2 feiTbQZdN2kiA5r+srnzPnOQnuUukV45xFs27NvwM3/sRB4uSLFegK39YAomZvz/0/D3 7HnQ== X-Gm-Message-State: AOAM533HSqvaYAgtV/HaXwGEV/jSrX1Ko+vvjbV9ylwU8IZanm7VhQ+E IJ8NFxpqjE/ycxWulLzZrNexUwFNXOZn6UO9Gf0= X-Google-Smtp-Source: ABdhPJzCs6O4wPSGsziPpySt0gU5EOg6MnElFEJmtIReR779zaP5sSaI8N0ka4QI+487ae0Fb7QeLCdHjDYG+uzPfZ0= X-Received: by 2002:a17:906:3b91:: with SMTP id u17mr21210040ejf.504.1604430587174; Tue, 03 Nov 2020 11:09:47 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 3 Nov 2020 19:09:34 +0000 Message-ID: To: Eugene Sidelnyk , PHP internals Content-Type: multipart/alternative; boundary="00000000000037344a05b3389b8f" Subject: Re: [PHP-DEV] Nullsafe From: george.banyard@gmail.com ("G. P. B.") --00000000000037344a05b3389b8f Content-Type: text/plain; charset="UTF-8" On Tue, 3 Nov 2020 at 19:08, G. P. B. wrote: > On Tue, 3 Nov 2020 at 19:05, Eugene Sidelnyk 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 > Just saw that you replied individually, please keep all discussion on list (i.e. reply all). Regards, George P. Banyard --00000000000037344a05b3389b8f--