Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128100
Precedence: bulk
MIME-Version: 1.0
References: <CAEPPVa2wXmb0pDKs4A7NyQ25Gaewz5n7JxBhaU1cxc=LpWzaPg@mail.gmail.com>
 <be95ae69-119f-4d39-bc42-4acb9ee295e1@sandfox.me> <CAEPPVa3EUy=YrQ91y2c4gKaSORYUunEcvDotQLjZ4yw0qKNz3A@mail.gmail.com>
 <CAAfnsFX1ru4QoU+xKbS3Ogo8M=My1idJ=PHVRD+BcTgNEZAYXA@mail.gmail.com>
 <CAEPPVa2ObVu0sjxK0SRAyp3AuU90-QToPAMZ4JxSuWfBC-uRCA@mail.gmail.com>
 <3c1e3111-32cd-4f2b-a525-e013e5b905cf@gmail.com> <CAEKnhAEHVtHVi79v4ry5mULQA=+t-B0wUS3BRFdDA5wyWNXdpQ@mail.gmail.com>
In-Reply-To: <CAEKnhAEHVtHVi79v4ry5mULQA=+t-B0wUS3BRFdDA5wyWNXdpQ@mail.gmail.com>
Date: Fri, 18 Jul 2025 09:38:37 +0900
Message-ID: <CAEPPVa1SDC8_j7zP-e0ryj49D3H2V3TEJ6yf71tr6gCT6rO1Ow@mail.gmail.com>
Subject: Re: [PHP-DEV] Oniguruma maintenance was ended on 2025-04-24
To: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: youkidearitai@gmail.com (youkidearitai)

2025=E5=B9=B47=E6=9C=8816=E6=97=A5(=E6=B0=B4) 21:37 Jakub Zelenka <bukka@ph=
p.net>:
>
> On Tue, Jul 15, 2025 at 6:44=E2=80=AFPM Niels Dossche <dossche.niels@gmai=
l.com> wrote:
>>
>> On 15/07/2025 09:26, youkidearitai wrote:
>> > 2025=E5=B9=B46=E6=9C=8819=E6=97=A5(=E6=9C=A8) 3:45 Peter Kokot <petk@p=
hp.net>:
>> >>
>> >> What about bundling Oniguruma to php-src/ext/mbstring/oniguruma again=
 as it once was already? This would make development easier to be located i=
nside php-src. However, everything put inside php-src has a questionable fu=
ture on its own. For example, to be buildable as a standalone library and u=
sed elsewhere.
>> >
>> > Hi,
>> >
>> > Surely, I think make sense to be include inside php-src.
>> > From GitHub comment
>> > (https://github.com/php/php-src/issues/18467#issuecomment-3044192511),
>> > FreeBSD will end to maintenance Oniguruma in 2026-12-01.
>> >
>> > Therefore, I think re-include Oniguruma inside php-src.
>> >
>> > Is require an RFC if re-include Oniguruma?
>>
>> Hi
>>
>> Yes.
>>
>> This also won't solve the problem.
>> The problem is that Oniguruma is currently not maintained, not that it's=
 unavailable. Bundling the library inside PHP does not solve that maintenan=
ce problem.
>
>
> Well bundling effectively means that PHP teams is responsible for fixing =
(at least the security) issues. So in some way it solves the problem for us=
ers. The question is whether the maintenance burden that it adds is worth i=
t.
>
> Kind regards,
>
> Jakub

Hi, all

Thanks for response.

Niels, Peter
I see. We dropped many extensions abandonment libraries in the past.
Maybe Oniguruma(mbregex) drop is make sense.

> Considering that (I hope/think) most developers have moved to UTF-8 for t=
heir encoding

Yes, Derick. I hope that we are moving forward to Unicode too.

> how useful is it to have a separate (and
> not-comptible-with-PCRE) regular expression engine still?

I don't know how useful is Oniguruma(mbregex).
But seems many uses it.
https://github.com/search?q=3Dmb_ereg+language%3APHP&type=3Dcode&l=3DPHP

Anyway, I agree simple regex engine, Only PCRE.

Jakub

> Well bundling effectively means that PHP teams is responsible for fixing =
(at least the security) issues.

Yes, that's right.

Therefore, I said ambiguous my position(drop support mbregex or still
support in re-include Oniguruma).
However, I want to support PCRE and drop support mbregex.


Regards
(Sorry for the weird way to respond)

Yuya
--
---------------------------
Yuya Hamada (tekimen)
- https://tekitoh-memdhoi.info
- https://github.com/youkidearitai
-----------------------------