"brian m. carlson" <sandals@xxxxxxxxxxxxxxxxxxxx> writes:
> Even for users who would like to target an older version of Windows,
> such as the no longer supported Windows 7, GCC and Clang are available.
> The LLVM suite, including Clang, is available pre-compiled for download
> free of charge. Using a different compiler is specifically proposed by
> Microsoft staff[1] as a solution for users who wish to build modern
> programs for MSVC versions which do not support modern C.
>
> As such, we can assume that Git can be safely compiled with C99 or C11
> support on all operating systems which receive security support, and
> even some which do not. Our CI confirms that this series passes all
> tests. Let's introduce a test balloon which checks for this support and
> fails with an error message if it is absent.
I do not have much against adopting nicer C99 language features in
principle, but I hope that we are not becoming too Linux centric
with "other than Linux, as long as Windows is OK in some form,
everything is peachy" mentality.
If there is a rogue implementation that claims to do C99 with
STDC_VERSION without properly supporting some language constructs we
care about, that would be bad. That is why I tend to prefer the
approach we have taken so far, validating selected features we care
about one by one with pointed weather balloon tests, over "the
compiler says it supports that version, so we trust them".
Perhaps we can do this, and a more pointed "break compilers without
variable decl in for() loop" change, at the same time. After the
latter turns out to be noise free, we can update CodingGuidelines.
Even when we clear C99 as the whole, I'd be hesitant to allow
certain things from the language (not because compilers do not grok
them, but purely from style and readability point of view). For
example, -Wdecl-after-statement is a good discipline to follow even
if your compiler allows them.
Thanks.
Documentation/CodingGuidelines | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git c/Documentation/CodingGuidelines w/Documentation/CodingGuidelines
index 45465bc0c9..5c32b29949 100644
--- c/Documentation/CodingGuidelines
+++ w/Documentation/CodingGuidelines
@@ -205,15 +205,16 @@ For C programs:
. since mid 2017 with 512f41cf, we have been using designated
initializers for array (e.g. "int array[10] = { [5] = 2 }").
+ . since early 2022 with YYYYYYY, we have been using variable
+ declaration in the for loop (e.g. "for (int i = 0; i < 10;
+ i++)").
+
These used to be forbidden, but we have not heard any breakage
report, and they are assumed to be safe.
- Variables have to be declared at the beginning of the block, before
the first statement (i.e. -Wdeclaration-after-statement).
- - Declaring a variable in the for loop "for (int i = 0; i < 10; i++)"
- is still not allowed in this codebase.
-
- NULL pointers shall be written as NULL, not as 0.
- When declaring pointers, the star sides with the variable
