Re: [PHP-DEV] Policy for procedural style in new additions

2021-06-07 Thread Dik Takken
On 07-06-2021 12:40, Nikita Popov wrote: > I think that not adding new procedural mirror APIs is pretty > uncontroversial at this point. I think one open question is regarding API > additions to existing classes with a mirror API -- should we keep adding > procedural functions in that case? I g

Re: [PHP-DEV] Policy for procedural style in new additions

2021-06-07 Thread Nikita Popov
On Thu, Jun 3, 2021 at 8:28 PM Mel Dafert wrote: > Hi internals, > After the RFC to add IntlDatePatternGenerator () was accepted, it was > brought up that the duplication of > procedural and OO style was not necessarily/useful anymore. > This already has some (old) precedent - in 2012, UConverter

Re: [PHP-DEV] Policy for procedural style in new additions

2021-06-03 Thread Christian Schneider
Am 03.06.2021 um 22:47 schrieb Kamil Tekiela :I love this idea. We should definitely make it official that procedural > style API is unfavourable and should not be added to new classes. > On top of that, I would be in favor of deprecating all existing procedural > APIs. > - It's making it more dif

Re: [PHP-DEV] Policy for procedural style in new additions

2021-06-03 Thread Kamil Tekiela
Hi Mel, I love this idea. We should definitely make it official that procedural style API is unfavourable and should not be added to new classes. On top of that, I would be in favor of deprecating all existing procedural APIs. - It's making it more difficult to maintain code in two variants - It's

[PHP-DEV] Policy for procedural style in new additions

2021-06-03 Thread Mel Dafert
Hi internals, After the RFC to add IntlDatePatternGenerator () was accepted, it was brought up that the duplication of procedural and OO style was not necessarily/useful anymore. This already has some (old) precedent - in 2012, UConverter was added to ext/intl (https://wiki.php.net/rfc/uconverter