Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:129175 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 0799E1A00BC for ; Sun, 9 Nov 2025 18:12:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1762711939; bh=p+Ni0kVt4tjFWvTJyoeQ+4qce9Vs9kz1yHkx3zMqHwE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=hEEAf517uhNRSd6OOTM+hVBHaiT5I9Fr1Y5+SLJssDbvaQFtpcPjYDEB0KJUGuHws Dza5qARRM/I7s8lOx9TlXh2GqrBV99fCN0/B/KW0ViUbG96wZp/Un5Xt6BduNPp6w0 kLAzbkZgbhx4nK+JlTc/6+fgSJ+1bQW6CZwcQYTgAGv+IPD0dx8n2GqCOqJbi8h/Vm WLDEKxFJgt3FvFZPmh7mOb/rexR62FDE6R1ZoCtTysPqpyFJShuN7W6U76yeSdJ7Aq ysoh/s/9Ven+j0Petr15b/L3WoaH/U+OMowduEsei4U4Vm9gPMPhHvAI9XVQ94HOKQ jkWEnYGYVozGw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BDC9B18004D for ; Sun, 9 Nov 2025 18:12:18 +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.6 required=5.0 tests=BAYES_50,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, 9 Nov 2025 18:12:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1762711932; bh=pi2wE24qEX7oqnY2IsxZFL2ofSHW4CM06BiOXSa3yeU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=B8AAT8QQALpwTEwqGnvpHQNpjLtTTdMDTZqmqGSLGUp43H8imUuNR4oxH0NCzCjCO Y/Jgsoz+QQK4vBlTcKYZsP5nfIPRZXxyteJXxOyyJbETri4wOIoEWOmSpWbvRF5HH2 YtTCwknFLOcrJddQZgyJasyUTY/7jlTtw+qkY33tsATdeilN1VbdZH4tGu3T8FKBAk tHTSl1PSZbtbB/S1VCNAoAtBWTU1DOcCXXG1u/lotdZm6+pfJYRdGS8A/+kKXl0kWo TlohvYirgAe0JGodqdg7fcD85AXiv4FDFVQkJ2eTkdrAdxuzz023qEWy4QeCZsp6nt oYyMlWkFGOgRw== Message-ID: Date: Sun, 9 Nov 2025 19:12:10 +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: Edmond Dantes Cc: Claude Pache , Seifeddine Gmati , internals@lists.php.net References: <96013f5a-8ce0-4738-87e6-109706408faa@bastelstu.be> Content-Language: en-US In-Reply-To: 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/9/25 18:54, Edmond Dantes wrote: > My main point was something entirely different. > If the tool chosen to solve the problem is not well suited, then no > matter what methods are used to avoid mistakes, > it turns into an ongoing struggle that only adds complexity and > increases the chance of error. Virtually every (design) decision to make is a trade-off. > I only gave one of many examples that will inevitably occur if you > rely on reference counting. And therefore making generic claims of “many problems” without specifying them is not conductive to a discussion to figure out: - If the stated problems are a problem in practice or if they are mostly theoretical. - Possible solutions to the problems (such as the “WeakReference capturing of arguments”). - If the described problem even exists or if it is based on a misunderstanding of either the RFC or PHP's existing behavior. Best regards Tim Düsterhus