Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130236 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 9F6951A00BC for ; Tue, 3 Mar 2026 12:05:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1772539555; bh=jXuu+zaUNcV2aymiXnwW1Hz2WJFi50C9S7/6+gK1yD0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=bWoYZ2fHkHMo4UxHoKoTloyjzXSiHObG9lZfoyQ5bX20MnamIH8fjqEa/BYMMDNPT lpZCJ/c93cK2avALEYMnbp8ksgbVqYHzR1pCJozpJJnuw12khYqGMrJPxi6r5jbeNg kQ5ZhbblTUTMTBLMUEHLoSTAVYGPeYmKLBtXQm+RIyDp80r9b640vmMQhWpwSrIozx n6XIXSOo/MD0JQm1+8dth+P17rnMRo6NLGtQscqcp3olfaUNzuVqsUfLPVDXfONegO GS8GwVM7y3ttY3Bjyorpku4T7UvXTrSZJFeQntdwPLT9zsdPv8y6MKUyvp+XnDdl/I FqO9q6g2PRq6A== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8541B18005A for ; Tue, 3 Mar 2026 12:05:54 +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 ; Tue, 3 Mar 2026 12:05:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1772539547; bh=DeIFanHHe6wXbQewkLZgd3JrkADqKK4ZUmCE5D+F/jw=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=QOKIWOPRd737Vp5Li0/D7YAkNd9cnp+ClMhReCnmq9sRmavcMBzHjQvRv681SSdmA l2dr3d/AzUy1NV2FoqxXpeNxfufW2EvxJn5vnGXqcWctfF5RQxsT4RJ9BsRNLPOZTg k50AJ75OogeKOtlJGVBuIuV0fsQLkDN/RTTbtWfjBe/NZ+Ma95asv73KVBxZ4veoYf pPotGBLoABWiQvp4y4X08k7be9NXhw892eQSD1HQhaXm9e+IdyOvDRsY9CXKcgZ0oc 50PUeGxzu6rFAu0qJAqvr0/ymXoU3m3EBjV98RgnJ3G5G9pjM+KUqHlH3OrLxZcngQ AMmEMu9FKn7eA== Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Tue, 03 Mar 2026 13:05:47 +0100 To: Pratik Bhujel Cc: internals@lists.php.net Subject: Re: [PHP-DEV] [DISCUSS] ext/snmp promote invalid-input warnings to ValueError In-Reply-To: References: Message-ID: <422d4359daed3261e135fb689be70711@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 Pratik Welcome to the list and thank you for your interest in contributing to PHP! Am 2026-03-03 07:30, schrieb Pratik Bhujel: > Since this is a BC change I want guidance on whether this direction is > acceptable and whether an RFC is required for this scope. > > If the direction is positive I can prepare the RFC next. An RFC to handle this in a generic fashion, without needing to discuss every extension and function individually was proposed yesterday (“Exempt input type and value validation from BC Break policy”): https://news-web.php.net/php.internals/130221. I recommend to wait for the results of that one (and possibly participate in the discussion) before proceeding. See also this email that I just sent: https://news-web.php.net/php.internals/130235 Best regards Tim Düsterhus