Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114662 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42669 invoked from network); 28 May 2021 22:40:57 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 May 2021 22:40:57 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E1B0F1804C3 for ; Fri, 28 May 2021 15:53:02 -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=-0.7 required=5.0 tests=BAYES_40,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail02.x-net.at (mail02.x-net.at [83.65.141.138]) (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 ; Fri, 28 May 2021 15:53:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail02.x-net.at (Postfix) with ESMTP id 7AB24380B36 for ; Sat, 29 May 2021 00:53:00 +0200 (CEST) Received: from mail02.x-net.at ([127.0.0.1]) by localhost (x-zimbra02.x [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 5cqYSDQF82Ss for ; Sat, 29 May 2021 00:52:59 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail02.x-net.at (Postfix) with ESMTP id B827E380B62 for ; Sat, 29 May 2021 00:52:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at x-t.at Received: from mail02.x-net.at ([127.0.0.1]) by localhost (x-zimbra02.x [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yDQmLU9X2TTU for ; Sat, 29 May 2021 00:52:58 +0200 (CEST) Received: from [127.0.0.1] (178.115.47.235.wireless.dyn.drei.com [178.115.47.235]) by mail02.x-net.at (Postfix) with ESMTPSA id 32DF2380B36 for ; Sat, 29 May 2021 00:52:58 +0200 (CEST) Date: Sat, 29 May 2021 00:52:58 +0200 To: internals@lists.php.net User-Agent: K-9 Mail for Android In-Reply-To: References: <1815820036.3212683.1621007783673.JavaMail.zimbra@dafert.at> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [VOTE] Add IntlDatePatternGenerator From: mel@dafert.at (Mel Dafert) >It's =2E=2E=2E checks calendar =2E=2E=2E the year 2021=2E Do we *really* n= eed to add a >procedural mirror APIs, especially with such auspicious function names as >datepatterngenerator_get_best_pattern? > >I believe the procedural APIs are considered legacy APIs, and we are >intentionally not adding them for new functionality=2E For example, the m= ost >recent intl addition (IntlChar) does not come with procedural APIs=2E I wasn't aware that there was a precedent with IntlChar - the documentatio= n seems to frame this duplication as a feature rather than a historical artifact= =2E (The wording "OO style vs procedural style" does not imply any endorsement of one style over the other to me=2E) However, i am open to only including the OO API if there is consensus - al= though I feel like this should maybe belong in a separate RFC that clarifies that= future additions should prefer the OO style, and that the OO style is the "preferred" one=2E