Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116556
MIME-Version: 1.0
References: <CALp5e-8xoj-RTcvmvDZ68c0pgAJBUcKhkLwZxNLspYhY6G6qEw@mail.gmail.com>
 <CAGBsUrcVjNmOJk8DnOmWzfmr5vVgjWbDzj-bYv1QGDXSdJz=Cw@mail.gmail.com>
 <CALp5e-8=sbQo1rCNW_Hf0Tw6v4PtPss7L9GoHq6XTev8Wh97=g@mail.gmail.com>
 <CA+kxMuRdb2DDNteEn1Os7T5dc-5gUCQ=eTB9Bfr7AA5bb4q2jg@mail.gmail.com>
 <CALp5e-92Te1ZmSKXubG45Fw1nznyiN2sN_LmycYZ1Dxb2YFQ4g@mail.gmail.com> <CAESVnVqD+9w=_qhh2ADD9WM0YqmGP_X0Qpfd8qZonbP2wZ4G_Q@mail.gmail.com>
In-Reply-To: <CAESVnVqD+9w=_qhh2ADD9WM0YqmGP_X0Qpfd8qZonbP2wZ4G_Q@mail.gmail.com>
Date: Thu, 2 Dec 2021 14:48:19 +0000
Message-ID: <CAFv4g+FCcOb6WWWPkzQhTmvMAj8p2vQGLDK5OymrykQkKYE8UA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000540ecd05d22ae295"
Subject: Allowing NULL for some internal functions
From: craig@craigfrancis.co.uk (Craig Francis)

--000000000000540ecd05d22ae295
Content-Type: text/plain; charset="UTF-8"

On Fri, 26 Nov 2021 at 16:47, Sara Golemon <pollita@php.net> wrote:

> I'm not saying send PRs to fix them all...  Let's make PHP better,
> together.



On a similar theme, trying to avoid too much work for developers upgrading
to later versions of PHP.

Is there any value in me proposing an RFC to update *some* internal
functions so they can accept NULL?

I see developers using their framework of choice for GET/POST/COOKIE/etc
values (where they receive NULL to represent unset values), or simply doing
`$q = ($_GET['q'] ?? NULL)`, and other sources... where they will now get
deprecation messages whenever they use functions like `htmlspecialchars()`,
`trim()`, `strpos()`, `strtoupper()`, `strlen()`.

For example, a search page, where the search term is defined in the URL
(e.g. "/search/?q=abc"), and that value is shown on the page, often in an
`<input type="search" name="q" value="?" />` for the user to edit, and
sometimes repeated in the page content (where they may use `strtoupper()`
for styling purposes, instead of doing that via CSS `text-transform:
uppercase`).

Craig


https://externals.io/message/116076

--000000000000540ecd05d22ae295--