Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114737 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68701 invoked from network); 5 Jun 2021 10:03:18 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Jun 2021 10:03:18 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2F9CD180507 for ; Sat, 5 Jun 2021 03:17:18 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from processus.org (ns366368.ip-94-23-14.eu [94.23.14.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 5 Jun 2021 03:17:17 -0700 (PDT) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by processus.org (Postfix) with ESMTPA id 448945101324; Sat, 5 Jun 2021 10:17:16 +0000 (UTC) To: Nikita Popov Cc: PHP internals References: <1e900fb5-4fb9-e283-de67-4fb1e035c0c8@processus.org> Message-ID: <9b1642d7-28bb-0f6b-d134-c6de570721bf@processus.org> Date: Sat, 5 Jun 2021 12:17:15 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Authentication-Results: processus.org; auth=pass smtp.auth=pierre-php@processus.org smtp.mailfrom=pierre-php@processus.org X-Spamd-Bar: / Subject: Re: [PHP-DEV] [RFC] Readonly properties From: pierre-php@processus.org (Pierre) Le 05/06/2021 à 12:06, Nikita Popov a écrit : > Yes, this is supported. What matters is the scope from which the > initialization occurs. If you rebind a closure to the scope of the class, > then you can perform any operations that would be legal inside that class, > including access to private properties and initialization of readonly > properties. > > Regards, > Nikita OK, I wasn't sure I thought I'd ask, this is nice, thank you ! I can't vote, but I love this RFC, thank you very much for this. I sincerely hope this will not get into flames. -- Pierre