Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129090 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 14AF51A00BC for ; Wed, 5 Nov 2025 16:27:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1762360048; bh=WjiRc6suznjXU5zOm01tyOtFgio5ud3fS/uIqPJQetg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=cnLUI/CJL0BIoVYxbZGSQzHFM625yaCxXW6DFL6KBrwjwU8uqpN4a0Nnrl5YETabJ GGthBiYXnvf4po4y61ldj33OJBRlVieS0ILhi3J5RFA/8+XCfgXJJQCHk8ugLPy9z5 xUpy/QmBJFl92cZJemrLfOfZ2e1Kds1sbOwYSIw1zAxs8yXCbx9m0UMkcOr9ZGO+xj 4QZiR5AoVk4iLCmNPxbOgBaz/IJTCmqt59LICZemXy3J+rURH945KQKFuOLv3oLUMO 5gt7ZvTPg4j61NGMfSUBiZERY/yJWgk5PckYhqQSYULjYXg18pzKkrcOCa6YSbvXat widkjZimt5GWA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EDF18180087 for ; Wed, 5 Nov 2025 16:27:27 +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 ; Wed, 5 Nov 2025 16:27:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1762360040; bh=cW5GLuXATjrrIyLk/drohjPRDNgKPX+Ts7MUD8iPlA0=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=nbm7fD4qaidEReEDbpvD5eMZqtbNNPEY/YHunK4QjWwD+Okx0qkfKZ6EPxLFPzU+/ 1Lr/AoqCE3HLIo6S9YlS6u+TD7U4MiCEOwLERJ1THfpS16FEa3/gl6gRnfnSt3FWIR CVXtf1J8HPuADzF8QxSF5bxy4l830k6G6ZZY3A4+K6YOwyPmIVBu6P+JQ4n1LUFCl1 2DWeTJu+jwWviHswt7R2ftz4iIbQAX/LB41PiI5o6wmXCGHK/1lGUxfe0HcyJAFlsO v5VB1y90GlzwP0MmI0rDW8QnKESvhTJ5BnclW5TTDMG1AzldZLo1b/a57TlZ+X7g50 NSeKDnr5UGLrQ== Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Wed, 05 Nov 2025 17:27:20 +0100 To: Seifeddine Gmati Cc: internals@lists.php.net Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping) In-Reply-To: <06a85ff1c20254733ba2e92927d06014@bastelstu.be> References: <06a85ff1c20254733ba2e92927d06014@bastelstu.be> Message-ID: <95c44f9cda53ddb78f993faaa9c0705b@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-04 16:50, 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. Best regards Tim Düsterhus