Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130222
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Subject: Re: [PHP-DEV] [RFC] Exempt input type and value validation from BC
 Break policy
Date: Mon, 2 Mar 2026 14:49:45 +0100
References: <Sm1GZb5hgsnp0GsxSRFcsRA5FiZoHJMi9368TSt4Qb8Qr61aFDSGxQMP9fpj58uMVwPgynuve8bplPhSZhR4HSnfHUCpoBqInTHWjd-uUyA=@gpb.moe>
To: PHP internals <internals@lists.php.net>
In-Reply-To: <Sm1GZb5hgsnp0GsxSRFcsRA5FiZoHJMi9368TSt4Qb8Qr61aFDSGxQMP9fpj58uMVwPgynuve8bplPhSZhR4HSnfHUCpoBqInTHWjd-uUyA=@gpb.moe>
Message-ID: <FAEFF35B-D1DB-4C1C-8F92-213EECDD6230@cschneid.com>
From: cschneid@cschneid.com (Christian Schneider)

Am 02.03.2026 um 14:13 schrieb Gina P. Banyard <internals@gpb.moe>:
> I would like to propose a short policy RFC to formally exempt input =
type and value validation from our BC Break policy.
> The current wording of the policy already permits us to add validation =
of inputs, but recently any such changes have been asked to submit an =
RFC instead.
> We believe that requiring an RFC for this type of change is =
detrimental and adds unnecessary friction for routine maintenance =
activity and new contributors.
>=20
> RFC: https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-policy

Playing my favourite broken record:
Can we please state that additions of Exceptions should (in most cases) =
go through an E_WARNING phase to allow a time window to fix code before =
changing the behaviour?

I'm fine with not needing an RFC for such changes as long as the =
migration process is being respected.

Regards,
- Chris
=20=