Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100916
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender)
To: Anatol Belski <ab@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <DB3PR0202MB3356096C7AF3921A95A7D4D0BA4F0@DB3PR0202MB3356.eurprd02.prod.outlook.com>
Message-ID: <00a67154-d008-46c6-ed62-49ca07aefaf4@gmx.de>
Date: Mon, 23 Oct 2017 16:23:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <DB3PR0202MB3356096C7AF3921A95A7D4D0BA4F0@DB3PR0202MB3356.eurprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] PCRE2 migration
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 16.10.2017 at 10:17, Anatol Belski wrote:

> I would like hereby to put the RFC about the PCRE2 migration for the 
> core https://wiki.php.net/rfc/pcre2-migration under discussion. A basic 
> port is available here https://github.com/php/php-src/pull/2857 for a 
> review.

Thanks, Anatol, for working on a PCRE2 compatible ext/pcre!

In my opinion, the only real issue is that the internal API would change
(the few userland affecting changes appear to be acceptable).  I can't
assess how many extensions actually use the public API of ext/pcre, but
this might be an issue regarding the adoption of PHP 7.3.

This said, I'm presently +0.9 on accepting the RFC.

-- 
Christoph M. Becker