Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114673
MIME-Version: 1.0
References: <1815820036.3212683.1621007783673.JavaMail.zimbra@dafert.at>
 <CAF+90c923S_sPfCCXoih1yg8OaePxALCj6urR3TszYOuqKhTgw@mail.gmail.com>
 <B57385A6-7D52-4461-B205-AE10057A0690@dafert.at> <0729fdcc-ece7-4261-ba28-9f72161495e6@www.fastmail.com>
 <DBA4E362-44CB-4581-935A-04619ABC5B2B@dafert.at> <3e8087a1-f8b3-3a7f-c048-6c61218d0710@gmx.de>
In-Reply-To: <3e8087a1-f8b3-3a7f-c048-6c61218d0710@gmx.de>
Date: Mon, 31 May 2021 11:40:31 +0200
Message-ID: <CAF+90c8wfa=Bua6t1ACNJP=E1BvuNwHLZqmrOHbK5XOTbe9qkg@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: Mel Dafert <mel@dafert.at>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002c2d6205c39d05ea"
Subject: Re: [PHP-DEV] [VOTE] Add IntlDatePatternGenerator
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000002c2d6205c39d05ea
Content-Type: text/plain; charset="UTF-8"

On Sat, May 29, 2021 at 4:25 PM Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> On 29.05.2021 at 10:02, Mel Dafert wrote:
>
> >> Agreed with Nikita.  There's no compelling reason to add double-API
> style anymore.  It may take a second RFC to modify this one to remove
> those, technically, but I'd vote for it.
> >
> > Should this new RFC then only apply to IntlDatePatternGenerator, or
> should it also
> > clarify that future additions to the intl extension (or to extensions in
> general?)
> > should not add both styles and prefer OO style if possible?
>
> IMO, an RFC which generally "forbids" the introduction of new dual APIs
> would make sense.  I don't think that we *need* an RFC to remove the
> procedural API of IntlDatePatternGenerator.
>

Right, for the purposes of this RFC, it's okay to just drop them if there
are no objections. A general policy RFC may still be useful for future
reference.

Nikita

--0000000000002c2d6205c39d05ea--