Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129409 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 6B25F1A00BC for ; Sun, 23 Nov 2025 15:33:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1763912041; bh=R7Q2uRVyOqvTqBelFVqwBC9vIHCQr21hXvWIkLNrgV4=; h=Date:Subject:From:To:References:In-Reply-To:From; b=bWo0rbBcvZDsYwjXV31wlkTpBmtaKDxDnS2Hv6+99YQ99DZ2inUsqX+Remq5yEiOj ilgCn89k5K6dKLnt6dCO3Rhi48yyJrsrXlU4ihiQ7LXq1dBL4jVbjnCZpLrT25jgtr T9/2iJ/ZbZS0igFPVUOAbqIqgofIBK8GSUMG7R/8ZYL7ho2i7XKngA2AxlZp1Ro628 Rzjv6AobVn7gfgIx2E0Fc5NsrMOv13n2WFQgWbPyunkJibokg738Tt5nb1ZkrilmJv AVGMV6FlSbMfnN2P1U4UUZ6IRYP4kHTlOXyrI7Y/NzzOwVyBDf24JLgwFeNacFCgPI iQSDu0/hqz7Ew== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 02F6B180040 for ; Sun, 23 Nov 2025 15:33:59 +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_40,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 ; Sun, 23 Nov 2025 15:33:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1763912032; bh=HkEwAyJDjduY2GmAi6BydZWz5Md/Vgxn7WG0/MHjomY=; h=Message-ID:Date:MIME-Version:Subject:From:To:References: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=fLDvWLcxnEPSZLNt799TmCnsr2+fYI617dz9wXFKH2H6LPl9Q8G4Mp0Xm7Xc+4Wrc ONpr63vOSZbQE7iM3r92kkMvLW50KKw9s23/SYa1VfEwaseJCUPLdGcg4aPQ1agGZn LfOLPhVr2XTGXUjQ4vdybtZWwaCbR3Y0h6SUYk7B6KZHMjYBfcu4MNXS7Ulg/PD8k6 2i0dxSbi9i/ClS6ogBUncoqTJDT/VS9y/9uMVEmMclFKZriNOjjw3Ssk70IQf5TvtF 2wBlHa07sXtPYpMP9zchkRRrQv6SuhPkiWT+8qi4ywjIRZQQUY3BGEDqWjvsewqeiB Hc+6X9CiUZLeQ== Message-ID: <5fd952fc-fc13-4c7d-b785-0b1338635f67@bastelstu.be> Date: Sun, 23 Nov 2025 16:33:51 +0100 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC][Discussion] use construct (Block Scoping) To: Seifeddine Gmati , internals@lists.php.net References: <99421ea8-b7ef-4049-aa74-31e8433309a8@bastelstu.be> Content-Language: en-US In-Reply-To: <99421ea8-b7ef-4049-aa74-31e8433309a8@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 On 11/23/25 15:29, Tim Düsterhus wrote: > The implementation should be up to date with the latest changes. The implementation was up to date, but one example in the RFC accidentally had an outdated error message (I've been made aware off-list). I've fixed the error message and also noted that the error messages are not final and not part of the actual RFC to allow some flexibility to enable the best possible error messages as part of the final review of the implementation. Best regards Tim Düsterhus