Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119302
MIME-Version: 1.0
References: <Y8U9B4AVP/R7vazI@swift.blarg.de> <CAFPFaM+FpJj0=Urdz-JUihtNENC_DbG+cKbwwiVNg4GNvZrdZA@mail.gmail.com>
 <Y8e1VLXmnZP66dSg@swift.blarg.de>
In-Reply-To: <Y8e1VLXmnZP66dSg@swift.blarg.de>
Date: Wed, 18 Jan 2023 11:51:28 +0000
Message-ID: <CAFPFaMJPt7ZfvfYmoWPGCfDuNW1tLPKwpxHaoy5+k3-RRaXovA@mail.gmail.com>
To: Max Kellermann <max+php@blarg.de>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="00000000000073821905f288704d"
Subject: Re: [PHP-DEV] RFC: rules for #include directives
From: george.banyard@gmail.com ("G. P. B.")

--00000000000073821905f288704d
Content-Type: text/plain; charset="UTF-8"

On Wed, 18 Jan 2023 at 09:01, Max Kellermann <max+php@blarg.de> wrote:

> On 2023/01/16 13:48, "G. P. B." <george.banyard@gmail.com> wrote:
> > Moreover, having those sorts of changes be RFCs seems counterproductive
> as
> > the only people who care about this are actual core and extensions
> > developers and this opens the gate for petty RFCs to resolve coding style
> > disagreements.
>
> How shall we proceed from here?  Shall I create an official RFC or
> not?
>
> George said no, which I understand; but I don't know what else to do
> to produce a decision.
>
> I asked Dmitry to post his GitHub arguments in this thread, so you see
> both sides of the story, and you can discuss his arguments.  (I
> already replied to him on GitHub, see
> https://github.com/php/php-src/pull/10345)
>

I still don't think the RFC process is a good vehicle for those sorts of
decisions, but it's the only process we have and there is some clear
disagreement that needs to get resolved here.
So I think creating an official RFC is the only way.

Best regards,

George P. Banyard

--00000000000073821905f288704d--