Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117181 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94791 invoked from network); 1 Mar 2022 16:04:01 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 1 Mar 2022 16:04:01 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E4B621804B4 for ; Tue, 1 Mar 2022 09:25:17 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS29838 64.147.123.0/24 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 1 Mar 2022 09:25:17 -0800 (PST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 1128C3200C46 for ; Tue, 1 Mar 2022 12:25:15 -0500 (EST) Received: from imap43 ([10.202.2.93]) by compute5.internal (MEProxy); Tue, 01 Mar 2022 12:25:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=+D0EjWHSBgjpX0ihC IB+T4ToKT3N8ynKR1Yhjw92nTM=; b=BSj+nfGasO292KSPmjySabg4qIGxJKGfy Sf6ld81OlRswvFLxoSzloH/ScUppay5f43PEpd2G78yuvpwZMjn1D31rbLtir8NL vf2wwmHYy3VQ+nc4F6HKnSgw4PDPpkRrKG18A3ZAy9dLuh4z+7s15V1czh6qr8Nf yjUOQDmcymvJ+X3bfp75DRo8DQql/NDpZXiyC0DlqE0QozHSjowxcb5Ojbn2JPde bX0IoDTcqZg8lcZEDzqDibK4a/3nu2X5RQrB1LSNMjLq0aZEMtXB7iiwexWBqRZ2 qxGPHg50xKLDrGf3LkbpEsoiAyJV1JdOYN7mixsVOLTep7mdhq+Hw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdfnrghr rhihucfirghrfhhivghlugdfuceolhgrrhhrhiesghgrrhhfihgvlhguthgvtghhrdgtoh hmqeenucggtffrrghtthgvrhhnpedthfffueffgfeltddthfeujeetleegjefgjeefveej ffdtffethfdtvdeuffegkeenucffohhmrghinhepvgigthgvrhhnrghlshdrihhopdhphh hprdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhho mheplhgrrhhrhiesghgrrhhfihgvlhguthgvtghhrdgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3E476AC0E99; Tue, 1 Mar 2022 12:25:15 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4778-g14fba9972e-fm-20220217.001-g14fba997 Mime-Version: 1.0 Message-ID: In-Reply-To: References: Date: Tue, 01 Mar 2022 11:24:54 -0600 To: "php internals" Content-Type: text/plain Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Sealed Classes From: larry@garfieldtech.com ("Larry Garfield") On Mon, Feb 28, 2022, at 9:49 PM, Saif Eddin Gmati wrote: > Hello internals, > > Following up on last years email, I have decided to move along with the > Sealed classes RFC after some changes, and put it up for discussion. > > Previous discussion: https://externals.io/message/114116 > RFC: https://wiki.php.net/rfc/sealed_classes Why not "final ... permits" or "final ... for" as options? Effectively what is created here is a final class/classic-thing, but with holes in it. Otherwise, there become questions about why final and sealed have different keywords when they're such similar things. --Larry Garfield