Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130091
Content-Type: text/plain;
	charset=utf-8
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] Grouped ValueError Conversions for PHP 8.6 (mkdir
 example)
Date: Wed, 18 Feb 2026 22:21:48 +0100
References: <CAO3bawn3io0dmp8uH41v6R218CM55cnVV18qm5N8Yie0X87zTg@mail.gmail.com>
To: internals@lists.php.net
In-Reply-To: <CAO3bawn3io0dmp8uH41v6R218CM55cnVV18qm5N8Yie0X87zTg@mail.gmail.com>
Message-ID: <E70150E9-DED0-4690-A1E4-44A188ECD5F7@cschneid.com>
From: cschneid@cschneid.com (Christian Schneider)

Am 18.02.2026 um 20:32 schrieb Muhammed Arshid KV =
<arshidkv12@gmail.com>:
> Following maintainer feedback, I=E2=80=99ve created an RFC to group =
multiple warning =E2=86=92 ValueError conversions for PHP 8.6 instead of =
proposing many small RFCs.
> The initial example includes mkdir() where invalid permission values =
(outside 0..07777) would throw ValueError instead of emitting a warning =
and returning false.

When converting something which has currently silently ignored (part of =
its) parameters to a ValueError Exception, you should add an E_WARNING =
phase to give developers a time window to fix their code.

Example:
	mkdir("foo", 070555));	# Currently does the same thing as 0555

The E_WARNING phase enables developers to catch writing 555 instead of =
0555, but it allows fixing the code without being a blocker for =
upgrading to PHP 8.6.

Regards,
- Chris