Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117171 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35617 invoked from network); 28 Feb 2022 23:13:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Feb 2022 23:13:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 47373180382 for ; Mon, 28 Feb 2022 16:34:46 -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=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 ; Mon, 28 Feb 2022 16:34:45 -0800 (PST) Received: by mail-lj1-f175.google.com with SMTP id bn33so19747056ljb.6 for ; Mon, 28 Feb 2022 16:34:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=craigfrancis.co.uk; s=default; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JCw/XZkrw1BaBMV5mg+AHyDh09JmD5jUi7hHeq8Bvy0=; b=AkbQWvmlvqRXMbMUeDoMsCzsG21fNU+Tf4NxTP04mknWOo1VCNF4zs+m2DmlaF2kmZ Iu8XEnOPz5k/eMgBzly2M4ri/++105Arx7E9O26zLLicjJcgML5wu3Qz1VjOtToLpVdR nRaNZWUXJzUuSips0mhzUkCtC/Xn71vzoenpY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JCw/XZkrw1BaBMV5mg+AHyDh09JmD5jUi7hHeq8Bvy0=; b=wE4o6ywx910pFmYMhzgio6lr8DgmzuguUkuw/1zg+/Ox1jGByS53FS4AgOJZSChF+8 SoS6hLYro+o/K6yFdKELvjAWAKLMHEnsm9Iv6XYjmO+qKVPtXKqIQ5+/K/rExN0OVlOs M2qSOLboD+1ieZKDdEfHCOheIUcWT+cH4mHB/Q/4ohVXraYNEjQK6SUH9ZX598ki6w8p VTBZib/j0NvZr7AyBFefp7P34h8v2lRthhIaOxndw56ZlFWHjHZcD61MlAeHQhzShxia nq8ofRC0WWdtqa1nnZ2pRKi4w5m4jHMeG8F+CoOgkQ5LY/liqcmUiIDkfPaOw3YAP3Jh SQwg== X-Gm-Message-State: AOAM531zmUah2YJHXuRZZFUrASEhdYI5vROAACdcDtEhQWlZnTlgvV+e 2rBZSI5vhlVMMZdaXRzbwKnuVrAYk4mWJpp5mS7miw== X-Google-Smtp-Source: ABdhPJyHBdDJspMI2jT/dAPD7OyEsHI6yYmi8zLegFafkn1+DXDb7D5ETqi+faq3I8AbIcxGvveJAjz+MTcsl7X5Fpg= X-Received: by 2002:a2e:b16e:0:b0:246:902:e470 with SMTP id a14-20020a2eb16e000000b002460902e470mr16758955ljm.21.1646094884182; Mon, 28 Feb 2022 16:34:44 -0800 (PST) MIME-Version: 1.0 References: <983552d8-11f1-b5bc-fb82-148347982fda@gmx.de> <5494eaa7-2fa6-8364-9683-a2c8c9789d81@gmail.com> In-Reply-To: Date: Tue, 1 Mar 2022 00:34:33 +0000 Message-ID: To: Guilliam Xavier Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="000000000000d6b19205d91d541f" Subject: Re: [PHP-DEV] Allowing NULL for some internal functions From: craig@craigfrancis.co.uk (Craig Francis) --000000000000d6b19205d91d541f Content-Type: text/plain; charset="UTF-8" On Mon, 28 Feb 2022 at 17:35, Guilliam Xavier wrote: > Call me devil's advocate, but is it too late to discuss revisiting past > decisions and consider changing direction towards 1 for userland functions > Hi Guilliam, tbh, for those who use `strict_types=1` nothing changes, so we can ignore them... for everyone else, nothing would break if user functions did start coercing NULL (if anything it just makes PHP more consistent)... whereas the current direction would add a Type Error exception for developers who aren't familiar with them, and those developers will just get annoyed at having to convert those NULL values manually (see the complaints from developers upgrading to PHP 8.1). Craig --000000000000d6b19205d91d541f--