Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121385
Return-Path: <tim@bastelstu.be>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 42239 invoked from network); 18 Oct 2023 12:38:56 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 18 Oct 2023 12:38:56 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id AF6331804D0
	for <internals@lists.php.net>; Wed, 18 Oct 2023 05:38:55 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS24940 176.9.0.0/16
X-Spam-Virus: No
X-Envelope-From: <tim@bastelstu.be>
Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Wed, 18 Oct 2023 05:38:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be;
	s=mail20171119; t=1697632733;
	bh=KH5k1ITRUCzgjAtwG+AKXpggxaHbv7wunza70mp5BoY=;
	h=Message-ID:Date:MIME-Version:Subject:To:References:From:
	 In-Reply-To:Content-Type:from:to:cc:subject:message-id;
	b=d9gwLst+AFXC5nkmDsloGcoiXVuqOefhLL5l7O9eolffhQPaR9F8MTFrZpkRAALcM
	 AOUuqR78XO4FDr60vvwFsL6ySJJVwo8y08IrAus/o5Dy3rITKSVhcMddX5zAF6R633
	 XM2KzNGePkxjPRWbtq07Rgb0oIuWn3fBo+0h5vPBrMq2ZQsvEQdl5Szm2ZkRNuXYm8
	 AUKkXze1EnodbuYe+CXaRc5xWFc+nvfImGvuZDkhVp4WACF2kefl3r4TWbP/bS/FtF
	 eW+gtnoW35o4f4g+sFoVI37oqz1Gr90YLH8TQKQ05TINRN6uEIrUGsss1o2Vboomca
	 jzc5JdH2w6x6g==
Message-ID: <9d1f5b61-8826-4449-9c74-a15a1f522574@bastelstu.be>
Date: Wed, 18 Oct 2023 14:38:53 +0200
MIME-Version: 1.0
Content-Language: en-US
To: PHP internals <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: 8bit
Subject: Re: [PHP-DEV] Deprecate posix_times
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 10/18/23 09:00, Christian Schneider wrote:
> 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.

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.

Best regards
Tim Düsterhus