Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119158
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2212151531360.462551@singlemalt.home.derickrethans.nl>
 <09aa499b-f5ec-5e80-63d8-6271fa87c390@heigl.org> <60ba972f-5b7c-f9ea-fb07-7b565bd108cd@bastelstu.be>
In-Reply-To: <60ba972f-5b7c-f9ea-fb07-7b565bd108cd@bastelstu.be>
Date: Thu, 15 Dec 2022 15:51:49 -0300
Message-ID: <CADK1yX+btXDOUJ2-43-LX2r0x8kTPp6YTvos9BOmf9D5NZGgng@mail.gmail.com>
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: Andreas Heigl <andreas@heigl.org>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003e7ec805efe259f3"
Subject: Re: [PHP-DEV] [RFC] Unicode Text Processing
From: deleugyn@gmail.com (Deleu)

--0000000000003e7ec805efe259f3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 15, 2022, 3:16 PM Tim D=C3=BCsterhus <tim@bastelstu.be> wrote:

>
> [1] The 'Text' class should likely be made final, because folks might
> otherwise rely on a specific userland extension, preventing actual
> interoperability.
>

I'm fond of final classes but in here I think it *adds* burden to core
developers. As you said it yourself having a Type within PHP will help
interoperability. Having this type be final will hurt interoperability
because everyone's wrapper will be different. This may lead to the
community requesting more changes to core.

>

--0000000000003e7ec805efe259f3--