Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121373
Message-ID: <94b5daba-22fa-49b8-9551-6f9a3b6ef13a@daniil.it>
Date: Wed, 18 Oct 2023 10:28:43 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: internals@lists.php.net
References: <a7ff0df5-bf67-4d94-8d13-7771e11fea47@daniil.it>
 <DBF4FE1F-C5B5-43BA-B1E9-53112D26492F@cschneid.com>
In-Reply-To: <DBF4FE1F-C5B5-43BA-B1E9-53112D26492F@cschneid.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecate posix_times
From: daniil@daniil.it (Daniil Gentili)

Hi,

As listed in my original thread, I think that offering posix_times 
without offering sysconf would be like offering a version of the 
microtime function, which returns a value divided by a *undocumented and 
unexposed divider that changes in each patch version of PHP*.

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.


Regards,

Daniil Gentili.

On 10/18/23 09:00, Christian Schneider wrote:
> Am 17.10.2023 um 19:39 schrieb Daniil Gentili <daniil@daniil.it>:
>> I would like to submit an RFC (and related PR) to deprecate posix_times for PHP 8.4, removing it for PHP 9.
> My question here would be: Is there sufficient reason to remove this function and introduce a BC break, i.e. is the implementation code hard to maintain or does the function cause security issues?
>
> Unless that is the case I'd leave it unchanged and just add a note to the documentation that people might want to consider using getrusage() instead.
>
> Regards,
> - Chris
>