Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126156
Feedback-ID: id5114917:Fastmail
Date: Sat, 21 Dec 2024 18:43:21 +0000
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Discussion: Remove file statcache?
User-Agent: K-9 Mail for Android
In-Reply-To: <CAEKnhAFU32EXh483QzR0LLUt+Jou4ejKjOXqBQ_G43wR7LW5cA@mail.gmail.com>
References: <27531d9d-9bfe-4acc-b9ab-80b1017e3038@app.fastmail.com> <CAEKnhAFU32EXh483QzR0LLUt+Jou4ejKjOXqBQ_G43wR7LW5cA@mail.gmail.com>
Message-ID: <ACB1A7C2-FAF5-4A43-BBB9-A3E8469E2385@rwec.co.uk>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")



On 21 December 2024 16:43:39 GMT, Jakub Zelenka <bukka@php=2Enet> wrote:
>I would prefer to disable it by default but keep some option (INI) to
>re-enable it=2E

Rather than a global setting, which would make behaviour even more unpredi=
ctable in libraries and out-the-box applications, I wonder if we could make=
 the cache explicit on the functions that use it?

I'm thinking for instance of an extra argument, like:=20

$perms =3D fileperms($name, statcache: true);
$size =3D filesize($name, statcache: true);

I'm not sure if this should default to false straight away, or be introduc=
ed gradually somehow, but it would make the behaviour much more explicit=2E

Regards,=20
Rowan Tommins
[IMSoP]