Re: RFC: rules for #include directives
| From: | G. P. B. | Date: | Wed, 18 Jan 2023 11:51:28 +0000 |
| Subject: | Re: RFC: rules for #include directives | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119302@lists.php.net to get a copy of this message | ||
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