Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129112 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 lists.php.net (Postfix) with ESMTPS id 7C2571A00BC for ; Thu, 6 Nov 2025 09:06:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1762420001; bh=GibKmnakgfIV5fqARQIGVx+SxBvk/48wwSDVqraTx6g=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=BjEgfAbaYWdN668eAmMBPWFSbOt7iRAK0xc9sXyWZvzljBRlAnf1ubfnU0WzLXBm6 qXA+a7rjiBhZ8G/bcdNY3ctaJf3mMqSLCTZgc4+CcuULHqDdAJIYVJ61/dVLwytK3K QE+ntRYuAykP4XRr/qvAbmeG3lSWmBkiQoxnorCOzIY4aBUln6agyi33tyg3rmwJ/v pX78QUfkWsftAcgE3fMkY2rNvBCHtZBLvo5389ZWdL9yqCbK22W/1l86b7qR1aFc/v 8+sgzwOJlOu/jOpqhOrQQEwsBMIG32/Q4nitc8FooMNBZ2W0DqDTqt3yeJO3jfjGQf TlXtYN6zdpFHA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 98991180088 for ; Thu, 6 Nov 2025 09:06:40 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (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 ; Thu, 6 Nov 2025 09:06:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1762419994; bh=TxDcUV0iiNH9nIsUvnD4yFglKjZMjuJHUNs26MHLEMk=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=aNWVekoc/aXw+XqDu473iAVua6VA6EAR/1eKBZ0pH5c3eB6n9sVBWOq1mRo0lflc2 VCPPJk+m+GD4gqkGSNbjgT5gXZcSWUbMzTYUpZ+feNnKvAcrHMUia3rEvdRAvJVaUh oBdjV87hfGldLJT+Hb1zYhTWOVofJ5wGTYL4lsY5XG22j1+ySHly7oQzbn0pIjS0Z5 z0n3GfER0r40uiz1Ji1XxpF8iVHQPgmxMAvkR/JyQCpYSph9nc/hRjKrPiUmEUYpBj vBJfmXM2HO811T8pPbs6egByYccEPooL9CQEX1ikhXKgEcw1NZxOtPs4Paps0Uzlk4 1kgDcnJ+WzOyA== Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Thu, 06 Nov 2025 10:06:34 +0100 To: Seifeddine Gmati Cc: internals@lists.php.net Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping) In-Reply-To: <95c44f9cda53ddb78f993faaa9c0705b@bastelstu.be> References: <06a85ff1c20254733ba2e92927d06014@bastelstu.be> <95c44f9cda53ddb78f993faaa9c0705b@bastelstu.be> Message-ID: <94204a28546147ff60c8a5f1c7c21af3@bastelstu.be> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi Am 2025-11-05 17:27, schrieb Tim Düsterhus: >> Given the immediate and clear unanimous responses preferring option B >> (restoring the original values), this is something we'll go with. I'll >> look into updating the implementation later this week and we'll then >> update the RFC based on the insights coming out of the implementation >> (e.g. the exact semantics and possible edge cases). > > I just updated the implementation in the branch already. The RFC text > will follow. The RFC text has also been updated now to describe and showcase the “Backup and Restore” logic that will result in the semantics expected from full block scoping. Best regards Tim Düsterhus