Re: [DISCUSSION] Deprecate mbregex in PHP 8.6 and maintenance version
| From: | Christoph M. Becker | Date: | Mon, 25 Aug 2025 10:36:02 +0000 |
| Subject: | Re: [DISCUSSION] Deprecate mbregex in PHP 8.6 and maintenance version | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-128551@lists.php.net to get a copy of this message | ||
On 25.08.2025 at 09:26, youkidearitai wrote:
> I improvement this RFC.
> https://wiki.php.net/rfc/eol-oniguruma
>
> Added more information about maintenance versions.
> What do you think about Oniguruma maintenance ended.
> Please watch and feel free to comment.
First, thank you for caring about this! I agree that we need a long
term solution for this issue. As I understand it, Oniguruma's greatest
advantage over PCRE2 is that it supports other character encodings than
Unicode and ANSI, so deprecating mbregex might be a problem for some users..
Still, the alternative would likely be to bundle liboniguruma, and I
don't think that would be a good idea. So deprecating mbregex as of PHP
8.6.0 seems prudent; if there would be lots of objections, we could
still reconsider.
Now I wonder how much trouble it would be to separate mbregex from
ext-mbstring. If that can be done with a reasonable amount of work,
that would likely be the best course of action (in addition to
deprecating mbregex). We could than move the extension to PECL/PIE, and
let users deal with it (I'm not happy what happened to ext-imap, but
it's still better than relying on an unmaintained library from a bundled
extension).
Christoph