Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119186
MIME-Version: 1.0
References: <alpine.DEB.2.23.453.2212151424240.462551@singlemalt.home.derickrethans.nl>
 <BN7PR05MB403334EA297BBDBD311FF3CCDEE69@BN7PR05MB4033.namprd05.prod.outlook.com>
 <0E149CE3-9124-4473-92FE-ABF11B585C77@php.net> <BN7PR05MB40339538DE789250610BDCA0DEE49@BN7PR05MB4033.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB40339538DE789250610BDCA0DEE49@BN7PR05MB4033.namprd05.prod.outlook.com>
Date: Mon, 19 Dec 2022 15:05:42 +0000
Message-ID: <CA+kxMuTJNP0C6ZUER063pfid+-dcR_mWR2mwrdzEiF1TYaCRZA@mail.gmail.com>
To: Theodore Brown <theodorejb@outlook.com>
Cc: Derick Rethans <derick@php.net>, PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [Vote] More Appropriate Date/Time Exceptions
From: Danack@basereality.com (Dan Ackroyd)

On Sun, 18 Dec 2022 at 16:48, Theodore Brown <theodorejb@outlook.com> wrote:
>
> why it's okay to make a BC break for the OO API,
> but not for the procedural API.

Because they are different APIs.

People who use OO apis are used to handling exceptions and would
expect failures in OO code to throw exceptions. That the DateTime OO
api isn't currently do so is not conformant to their expectations.

People who use the procedural apis of DateTime, or procedural versions
of the Intl functionality (e.g. NumberFormatter vs
numfmt_format_currency) claim to prefer checking
date_get_last_errors(),  numfmt_get_error_code()  etc., rather than
have to worry about exceptions.

Changing the procedural functions to use exceptions would be a bigger
and more controversial change than the one proposed in this RFC.

cheers
Dan
Ack