Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118297
MIME-Version: 1.0
In-Reply-To: <4a473f00-e68f-54de-fc70-f6f94885464a@gmx.de>
References: <CAKVXxD9TDf2Hej4v7OLcNbcPa3Pv30XSry5CnrqHQ2X0suY-NA@mail.gmail.com>
 <4a473f00-e68f-54de-fc70-f6f94885464a@gmx.de>
Date: Sat, 23 Jul 2022 10:36:47 +1000
Message-ID: <CAKVXxD8piWGyrqpcjCkptGKg4pRuannwTvfmt=YQGROZuc03WQ@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000598d2405e46e255d"
Subject: Re: Character range syntax ".." for character masks
From: mickmackusa@gmail.com (mickmackusa)

--000000000000598d2405e46e255d
Content-Type: text/plain; charset="UTF-8"

>
>
>
 If I seek to have a round of voting for an RFC on character ranges in
character mask parameters, should I propose it for PHP8.3 or a higher
version?
I have only identified 4 native string functions that make reasable
candidates to join the 7 existing functions with this feature.

I don't think there is any benefit in explaining how these functions work.
The sole purpose for this change (and the reason that other functions have
it already) is to reduce code bloat without needing any extra function
calls.  If the feature is good enough for the first 7 functions, then it
should be good enough for these other 4 functions.

Breaking change possibility: if code is silly enough to repeat ANY
characters in the mask AND the repeated character is a dot between two
other characters, then I don't have much sympathy.   Honestly though, we
are talking about a super unlikely occurrence.

 Some demos: https://3v4l.org/2Y0q4

Mick

--000000000000598d2405e46e255d--