Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124051
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 qa.php.net (Postfix) with ESMTPS id D116B1A009C
	for <internals@lists.php.net>; Sat, 29 Jun 2024 17:18:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail;
	t=1719681611; bh=HS39cqgL/HP/WrBpYE2eIOQS1fCHRCX5BPujVVnUWTo=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To:From;
	b=mHBOI2/a9G5DD2fGmRkpDbX1z/3uy9xRpfqre4ZXJuVI7umBxNZC8rZ5aaUOat7d/
	 9uCLhzyUCsuhMRhDpDtmbuWvBp0XiKz/O1QWwPkQPosdoixpa4npF7xf2HUN3XAK4g
	 xFWOqW3RJWtwlwMgCToMEcUcwS4Al6r74MnQLvV4fKz92Absr+GgemisQGV8AtRRpM
	 2mUE2QKwMmdOlQV6aeoyKpunk/jD8Nk59PCWkyQNZWltlkabBe8ZRiJj3xt59dq8TQ
	 vuYWUe94WfOPhs9ynaJzGZsQ2UL5H9vLewUF3Kyz6N/QCD3bSOlLNSF0ySIySQY4LR
	 VDwi+4Lq9BcWg==
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 96CE31805FA
	for <internals@lists.php.net>; Sat, 29 Jun 2024 17:20:09 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,HTML_MESSAGE,
	MIME_QP_LONG_LINE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE
	autolearn=no autolearn_force=no version=4.0.0
X-Spam-Virus: Error (Cannot connect to unix socket
	'/var/run/clamav/clamd.ctl': connect: Connection refused)
X-Envelope-From: <saki@sakiot.com>
Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216])
	(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 <internals@lists.php.net>; Sat, 29 Jun 2024 17:20:08 +0000 (UTC)
Received: from smtpclient.apple (unknown [117.55.37.250])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id DCE704011B;
	Sun, 30 Jun 2024 02:18:46 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1719681526;
	bh=HS39cqgL/HP/WrBpYE2eIOQS1fCHRCX5BPujVVnUWTo=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To:From;
	b=U+f5Fgex7LXfJhTPV1htJ88jwLKBAWz9I4XbesAQ34gHIljjMn+F9SzA5Z/W6CxxR
	 lFf0oZc+9ONuraZSorAEKtYQmM6aMBXAk9zjsTj6zJnYsW9bYJnulEkPOQWTPZjn+n
	 2SQQkEfRgGRYD1dgP+xZgZQD9FzMH+A4w58NmCSU=
Content-Type: multipart/alternative; boundary=Apple-Mail-D03B92B0-9A9E-4FFC-9BBE-1FCDEF7542CD
Content-Transfer-Encoding: 7bit
Precedence: bulk
list-help: <mailto:internals+help@lists.php.net
list-unsubscribe: <mailto:internals+unsubscribe@lists.php.net>
list-post: <mailto:internals@lists.php.net>
List-Id: internals.lists.php.net
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] [RFC] Make the GMP class final
Date: Sun, 30 Jun 2024 02:18:34 +0900
Message-ID: <2F2CCA08-A722-48AF-8669-8F29F756D978@sakiot.com>
References: <2516a3d5-99fe-44f5-8279-00fca21ca545@barneylaurance.uk>
Cc: internals@lists.php.net
In-Reply-To: <2516a3d5-99fe-44f5-8279-00fca21ca545@barneylaurance.uk>
To: Barney Laurance <barney@barneylaurance.uk>
X-Mailer: iPhone Mail (21F90)
From: saki@sakiot.com (Saki Takamachi)


--Apple-Mail-D03B92B0-9A9E-4FFC-9BBE-1FCDEF7542CD
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,
>> If this RFC passes to make the \GMP class final, and your RFC passes to=20=

>> allow extending the \GMP class, then I think we=E2=80=99re in a sort of w=
eird=20
>> limbo state.
> Presumably in that case whichever RFC passes last would have to take prece=
dence. The community is allowed to change its mind.
>=20
I agree with Barney. If this RFC were to be passed before the other, it woul=
d necessarily override this one, since the other proposal assumes that class=
es can be inherited.

And the chances of that happening are probably close to zero at this point.

Regards,

Saki=

--Apple-Mail-D03B92B0-9A9E-4FFC-9BBE-1FCDEF7542CD
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Hi,=
</div><blockquote type=3D"cite"><div dir=3D"ltr"><blockquote type=3D"cite" c=
ite=3D"mid:EC5AF1B3-F72E-456E-AE6B-5D306C61079A@benramsey.com"><pre>If this R=
FC passes to make the \GMP class final, and your RFC passes to=20
allow extending the \GMP class, then I think we=E2=80=99re in a sort of weir=
d=20
limbo state.</pre>
    </blockquote>
    <p>Presumably in that case whichever RFC passes last would have to
      take precedence. The community is allowed to change its mind.</p></div=
></blockquote><div>I agree with Barney. If this RFC were to be passed before=
 the other, it would necessarily override this one, since the other proposal=
 assumes that classes can be inherited.</div><div><br></div><div>And the cha=
nces of that happening are probably close to zero at this point.</div><div><=
br></div><div>Regards,</div><div><br></div><div>Saki</div></body></html>=

--Apple-Mail-D03B92B0-9A9E-4FFC-9BBE-1FCDEF7542CD--