Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121581
Message-ID: <5338b761-e03f-4229-8f75-c16e415b65f9@bastelstu.be>
Date: Sat, 4 Nov 2023 12:40:34 +0100
MIME-Version: 1.0
To: Jakub Zelenka <bukka@php.net>, daniil@daniil.it
Cc: internals@lists.php.net
References: <a7ff0df5-bf67-4d94-8d13-7771e11fea47@daniil.it>
 <CAEKnhAHF9WYOGZCLFMvKd2tyrCgZHrcEfi7Nf538BTSV+JM6eQ@mail.gmail.com>
 <9d9acbd8-0b92-419e-b9c6-d7e35d0748dd@daniil.it>
 <CAEKnhAF9umc+nTiz1gT1cKJOaj7hkFNhuPReVfTSjhHYP3kVsA@mail.gmail.com>
 <7443be7f-0e78-49e1-ac2e-e33d04e76247@daniil.it>
 <CAEKnhAFC-j=1q3Dk37=diwi3bm5z_hm4c9AdWYWJVMOdQaJ3Ag@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAEKnhAFC-j=1q3Dk37=diwi3bm5z_hm4c9AdWYWJVMOdQaJ3Ag@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Deprecate posix_times
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 11/3/23 21:51, Jakub Zelenka wrote:
>> The main reason I would like to see this deprecated is not the fact that
>> it's returning a less precise value compared to getrusage, but rather
>> because it's returning a value that cannot be interpreted in any way
>> from pure PHP.
> 
> So if the constant is added, which is trivial, then the only reason left is
> that it's returning slightly less precise value and maybe slightly harder
> way to interpret it, right? If so, then I don't think this is enough to
> break BC. It would be much better done using documentation where we should
> also add a note about the new constant.

There is no real backwards-compatibility break, because the function was 
not correctly usable in the first place. This means that anyone who 
currently uses the function already has broken code.

An actual deprecation would make any existing user of the function aware 
of the fact that their code is broken. Just adding the necessary 
constant will not unbreak existing broken code, it will just enable 
users to use the function correctly going forward, *if* they read the 
documentation. Users relying on existing tutorials or StackOverflow 
answers will continue to have broken code.

Best regards
Tim Düsterhus