Phillip Wood <phillip.wood123@xxxxxxxxx> writes:
> On 15/07/2025 17:24, Junio C Hamano wrote:
>> That sounds good. I was wondering if it is easier to keep track of
>> things to add a new section to the CodingGuildlines document,
>> perhaps like this?
>
> That's a good idea
>
> Thanks
>
> Phillip
I guess I dropped the ball after this exchange. So our tentative
conclusion was to drop your new test balloon, and replace it with
the documentation patch you are responding to, which I obviously
am OK with.
Let me make it happen.
Thanks.
>
>> Documentation/CodingGuidelines | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>> diff --git c/Documentation/CodingGuidelines
>> w/Documentation/CodingGuidelines
>> index 6350949f2e..dd3dbb9c57 100644
>> --- c/Documentation/CodingGuidelines
>> +++ w/Documentation/CodingGuidelines
>> @@ -298,6 +298,14 @@ For C programs:
>> . since late 2021 with 44ba10d6, we have had variables declared in
>> the for loop "for (int i = 0; i < 10; i++)".
>> + C99 features we have test balloons for:
>> +
>> + . since late 2024 with v2.48.0-rc0~20, we have test balloons for
>> + compound literal syntax, e.g., (struct foo){ .member = value };
>> + our hope is that no platforms we care about have trouble using
>> + them, and officially adopt its wider use in mid 2026. Do not add
>> + more use of the syntax until that happens.
>> +
>> New C99 features that we cannot use yet:
>> . %z and %zu as a printf() argument for a size_t (the %z
>> being for
