Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121560
Date: Fri, 3 Nov 2023 00:11:40 +0100 (GMT+01:00)
To: Jakub Zelenka <bukka@php.net>, internals@lists.php.net
Message-ID: <9d9acbd8-0b92-419e-b9c6-d7e35d0748dd@daniil.it>
In-Reply-To: <CAEKnhAHF9WYOGZCLFMvKd2tyrCgZHrcEfi7Nf538BTSV+JM6eQ@mail.gmail.com>
References: <a7ff0df5-bf67-4d94-8d13-7771e11fea47@daniil.it> <CAEKnhAHF9WYOGZCLFMvKd2tyrCgZHrcEfi7Nf538BTSV+JM6eQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_39_99310529.1698966700318"
Subject: Re: [PHP-DEV] Deprecate posix_times
From: daniil@daniil.it

------=_Part_39_99310529.1698966700318
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi, I would like to echo the sentiment expressed by Tim earlier in another subthread:

>If a function cannot be safely or correctly used at all, then it shouldn't exist, especially if there are working alternatives [1].
>
>Expecting users to find a warning in the docs to learn that they should "never" use a function is not good developer experience.

I am aware that the function is defined by the POSIX standard but

1) Not all POSIX functions are currently exposed by the POSIX extension, sysconf being one of the missing ones (with IMO no good reason to add it)
2) I am not aware of the historical reasons that lead to the addition of a duplicated, less capable function to the POSIX standard (I'm super duper sure there's some reason related to an implementation detail of some 30+ year-old platform :), but PHP isn't a POSIX-compliant OS, it is not PHP's task to expose the entirety of the POSIX standard functions: PHP's task is to provide a simple to use language that also exposes some *useful* functions from the POSIX standard, and posix_times does not fit the definition, in my opinion.

Regards,
Daniil Gentili.

------=_Part_39_99310529.1698966700318--