Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126157
Message-ID: <21dd9ac7-e81b-4509-bfa4-a36d05237270@gmail.com>
Date: Sat, 21 Dec 2024 19:49:46 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Discussion: Remove file statcache?
To: internals@lists.php.net
References: <27531d9d-9bfe-4acc-b9ab-80b1017e3038@app.fastmail.com>
 <CAEKnhAFU32EXh483QzR0LLUt+Jou4ejKjOXqBQ_G43wR7LW5cA@mail.gmail.com>
 <ACB1A7C2-FAF5-4A43-BBB9-A3E8469E2385@rwec.co.uk>
Content-Language: en-US
In-Reply-To: <ACB1A7C2-FAF5-4A43-BBB9-A3E8469E2385@rwec.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
From: dossche.niels@gmail.com (Niels Dossche)

On 21/12/2024 19:43, Rowan Tommins [IMSoP] wrote:
> Rather than a global setting, which would make behaviour even more unpredictable 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: 
> 
> $perms = fileperms($name, statcache: true);
> $size = filesize($name, statcache: true);

In my opinion, this will become very messy.

> 
> I'm not sure if this should default to false straight away, or be introduced gradually somehow, but it would make the behaviour much more explicit.

Changing a default would be another BC break.

> 
> Regards, 
> Rowan Tommins
> [IMSoP]

Kind regards
Niels