Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128082 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 08F911A00BC for ; Wed, 16 Jul 2025 12:41:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1752669556; bh=tf6UW9m28HRClBSbqEKlBu5v+MkbNavo0dCH3h4tuPQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=GKTsA/96GvV+qm1BeAgtFLYphHhdECGF8C5/1GMfWKls8uk9Ts9SyRuJEW18FW7tm TeEEoHnajhxvwoqiIvJdm3ThaGPBxYooo+mtcKz7wd8UfPmsHAvibX5vwo2MgEUxpQ fu5RoMEzMuwSHaT4ujkJ2bae/6n1P1jLt+UEh5OgrC6qdpE/G6rbPfF0le4v0q/LzF FDHHlzZQGinoVDtSclfEaQRuPB2sK76B239kHVxEQHGfhr6B9MZDlQpQffO/ECYaVc xioL40tjy0VO7j/AJkueTNndGv6XrJmqEtSW0CFUPYxBr8PzrCWQ49I9ENvBpWJ05v CSx3Z8NXucl3Q== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2C28B18005D for ; Wed, 16 Jul 2025 12:39:15 +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=3.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_PASS, SPF_SOFTFAIL autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 16 Jul 2025 12:39:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1752669661; bh=tf6UW9m28HRClBSbqEKlBu5v+MkbNavo0dCH3h4tuPQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=HG5JEtlbBRMMc+hxtNW/scAXJXOLXuN+BMGoIFxdHNqVlrJD4LoLig0Xq/UwkuZkt FNWEjyAsB8+r84hdZwY5YicdA3Q4fCyBtV4Ds89+VCBtfV/go28t/D8Lhy4Xlhas/o LFHB9RaA32Ev1Nu7x5QmY90SOiWkLhgDLlVMp5MvK0nNxinD4SY3f3c9rLIUiT1yrg DoxWXzb26wECEFZyHg+eAwu+1hcf2aKfFhlMVb+QG+3t6vCame6v17BQtojbgYrjXB qBKVPUEsujjo2Xgz8iTidMSFxEcthYjNS8zTUBLeRe/Tmt0DuLfIaEndQT437z6Gac O4Wj6OLeFeT9w== Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 5FAB110C033; Wed, 16 Jul 2025 13:41:01 +0100 (BST) Date: Wed, 16 Jul 2025 13:41:01 +0100 (BST) To: "Gina P. Banyard" cc: PHP internals Subject: Re: [PHP-DEV] [RFC] Warnings for PHP 8.5 In-Reply-To: Message-ID: <97fb484b-e668-951b-efae-7baef28e444e@php.net> References: Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII From: derick@php.net (Derick Rethans) On Mon, 14 Jul 2025, Gina P. Banyard wrote: > Similar to the mass deprecation RFC, I would like to propose the > addition of a few warnings in certain situations: > https://wiki.php.net/rfc/warnings-php-8-5 > > I am expecting these 4 sub-proposals to be mostly uncontroversial, > other than possibly, the "Using offsets on non-container values in > isset()/empty()" one. That one seems to miss examples in the RFC as well. It might be useful to add those. Having said that, I am unsure as why I would want to see a way how isset/empty behave in either the "using offsets on non-container values" or "using invalid offset types" cases. These language constructs are often used as a guard in (albeit likely older *code*), and hence, this now throwing a warning doesn't really add anything for the developer. I'm also curious to know whether you or somebody else has checked what the effect of this change on existing code bases would be? cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/support mastodon: @derickr@phpc.social @xdebug@phpc.social