Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128174 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id B515A1A00BC for ; Tue, 22 Jul 2025 09:11:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1753175361; bh=5O/VgLicsSDOtOclmNXHqpsGPG8KTSp0vYoH31ZpAP4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Q68XNpHJYeYcu03kGLiqNBi5ouwsAUxZokJG+FcRVe25I/YdmpaFB0ErXM5I0oEAn kn9PT19SrfJa46/OGb6PBnvrjIOW+24M4M+zNhUB70W4lr3/fJgqbVrvBHKTOrmnQx RqXUOgCM4v9A/OFZAZ46KaRIC02DXzVL7MbvxW0liHZsGkQHKF39m8So3tjsOVWa9r Vbx2IH5A+XD/b/SC7L+KsnATNh7ALwC1crP+fd7GzOTI7ycpPgITSCU1vX0uv4a4yR AudhvTD3mBwPHSo7xmdI2nv2szuYeck7EFOLohnxGlnd/nuMRhYnISmnYa1UTiq7gk M4u67OelciScg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B527718006C for ; Tue, 22 Jul 2025 09:09:19 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: **** X-Spam-Status: No, score=4.7 required=5.0 tests=BAYES_50,DMARC_NONE, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from 2.mo583.mail-out.ovh.net (2.mo583.mail-out.ovh.net [178.33.109.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 22 Jul 2025 09:09:19 +0000 (UTC) Received: from director11.ghost.mail-out.ovh.net (unknown [10.110.58.226]) by mo583.mail-out.ovh.net (Postfix) with ESMTP id 4bmWhk479vz5yhd for ; Tue, 22 Jul 2025 09:11:02 +0000 (UTC) Received: from ghost-submission-5b5ff79f4f-chxxw (unknown [10.108.42.231]) by director11.ghost.mail-out.ovh.net (Postfix) with ESMTPS id 2A40CC2DAE for ; Tue, 22 Jul 2025 09:11:02 +0000 (UTC) Received: from php.earth ([37.59.142.100]) by ghost-submission-5b5ff79f4f-chxxw with ESMTPSA id gkL3MaVVf2jKYQAAhFd5ag (envelope-from ) for ; Tue, 22 Jul 2025 09:11:02 +0000 Authentication-Results:garm.ovh; auth=pass (GARM-100R003f3a9cae9-20f1-40bf-8131-ff8cf67e3e2d, 839A1FE1F85B840CE06DF1CC56A3031177C7FBB0) smtp.auth=peter.kokot@php.earth X-OVh-ClientIp:209.85.221.182 Received: by mail-vk1-f182.google.com with SMTP id 71dfb90a1353d-5313a2566f9so2134234e0c.0 for ; Tue, 22 Jul 2025 02:11:01 -0700 (PDT) X-Gm-Message-State: AOJu0YwNK2XpwkyWszKEmRLxuM/kN5bH5y7wf1HW8sWn18WQvuneKzfc 7emLnuglQOO/CFEyD23c2VSR3ED5c6lO7lj8+UkTxZNfhwdJ7BgNRrjPyOr0K3UKG3qtP/HJtT1 rcDyzU1WWoVcZK+FA6CLW0zAUQMXhg94= X-Google-Smtp-Source: AGHT+IFpUQ981nq3ktufstf5nyb1ChFumJbN2+IuBuPtW+YDg+LUdn3FayPIies1YDDmwPRBsU8DmSLGLQNP1fMUBjM= X-Received: by 2002:a05:6122:1e13:b0:535:aea0:795a with SMTP id 71dfb90a1353d-5373e2645f6mr12283338e0c.1.1753175460973; Tue, 22 Jul 2025 02:11:00 -0700 (PDT) Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 References: <3c1e3111-32cd-4f2b-a525-e013e5b905cf@gmail.com> In-Reply-To: Date: Tue, 22 Jul 2025 11:10:49 +0200 X-Gmail-Original-Message-ID: X-Gm-Features: Ac12FXwCdw_-juqWQHZTxZGxjdYcnWuxn3z4nR4w6hXS7v5h_XELvzCOHByVMKY Message-ID: Subject: Re: [PHP-DEV] Oniguruma maintenance was ended on 2025-04-24 To: youkidearitai Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary="0000000000009492ce063a80f84d" X-Ovh-Tracer-Id: 6171620342951305734 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdejgeehudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecunecujfgurhepgghfjgfhfffkuffvvegtsegrtderredttdejnecuhfhrohhmpefrvghtvghrucfmohhkohhtuceophgvthhksehphhhprdhnvghtqeenucggtffrrghtthgvrhhnpeeuhfehueeghfeggfejgffhudfgkeekfeeitdffgefhvdelvddtfeelieeltedtleenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhtvghkihhtohhhqdhmvghmughhohhirdhinhhfohenucfkphepuddvjedrtddrtddruddpvddtledrkeehrddvvddurddukedvpdefjedrheelrddugedvrddutddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpehpvghtkhesphhhphdrnhgvthdpnhgspghrtghpthhtohepuddprhgtphhtthhopehinhhtvghrnhgrlhhssehlihhsthhsrdhphhhprdhnvghtpdfovfetjfhoshhtpehmohehkeefmgdpmhhouggvpehsmhhtphhouhht From: petk@php.net (Peter Kokot) --0000000000009492ce063a80f84d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 18 Jul 2025 at 03:01, youkidearitai wrote= : > 2025=E5=B9=B47=E6=9C=8816=E6=97=A5(=E6=B0=B4) 21:37 Jakub Zelenka : > > > > On Tue, Jul 15, 2025 at 6:44=E2=80=AFPM Niels Dossche > 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 : > >> >> > >> >> What about bundling Oniguruma to php-src/ext/mbstring/oniguruma > again as it once was already? This would make development easier to be > located inside php-src. However, everything put inside php-src has a > questionable future on its own. For example, to be buildable as a > standalone library and used 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 > maintenance problem. > > > > > > Well bundling effectively means that PHP teams is responsible for fixin= g > (at least the security) issues. So in some way it solves the problem for > users. The question is whether the maintenance burden that it adds is wor= th > it. > > > > 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 > their 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 fixin= g > (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 > ----------------------------- I still think that Oniguruma needs to be bundled to make builds simpler. Deprecating this part of the mbstring extension will take until PHP 9 to be able to remove it (at least according to current PHP practices - deprecation and removal phase). And in the meantime PHP can be at least built with Oniguruma. Otherwise, there will be a situation where PHP 8.5 will have the option to enable mbregex functionality, while Oniguruma can't be found in the distribution packages (not downloadable through packages). If these functions can be replaced with the PCRE regular expressions, that's fantastic. --0000000000009492ce063a80f84d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 18 Jul 2025 at 03:01, youkidearitai &= lt;youkidearitai@gmail.com&g= t; wrote:
2025= =E5=B9=B47=E6=9C=8816=E6=97=A5(=E6=B0=B4) 21:37 Jakub Zelenka <bukka@php.net>:
>
> On Tue, Jul 15, 2025 at 6:44=E2=80=AFPM Niels Dossche <dossche.niels@gmail.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 Koko= t <petk@php.net>= ;:
>> >>
>> >> What about bundling Oniguruma to php-src/ext/mbstring/oni= guruma again as it once was already? This would make development easier to = be located inside php-src. However, everything put inside php-src has a que= stionable future on its own. For example, to be buildable as a standalone l= ibrary and used 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 tha= t it's unavailable. Bundling the library inside PHP does not solve that= maintenance problem.
>
>
> Well bundling effectively means that PHP teams is responsible for fixi= ng (at least the security) issues. So in some way it solves the problem for= users. The question is whether the maintenance burden that it adds is wort= h it.
>
> 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 fo= r their 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/s= earch?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 fixi= ng (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
--------------------------= ---=C2=A0

I still think that Oniguruma need= s to be bundled to make builds simpler. Deprecating this part of the mbstri= ng extension will take until=C2=A0PHP 9 to be able to remove it (at least a= ccording to current PHP practices - deprecation and removal phase). And in = the meantime PHP can be at least built with Oniguruma. Otherwise, there wil= l be a situation where PHP 8.5 will have the option to enable mbregex funct= ionality, while Oniguruma can't be found in the distribution packages (= not downloadable through packages).=C2=A0If these functions can be replaced= with the PCRE regular expressions, that's fantastic.
--0000000000009492ce063a80f84d--