fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! Fix #1473: warn when fclose() is used as a while loop condition

francois-berder · francois-berder · commit 30ed3691fdce · 2026-05-16T17:06:44.000+02:00
diff --git a/releasenotes.txt b/releasenotes.txt
@@ -8,6 +8,7 @@ New checks:
 - MISRA C 2012 rule 10.3 now warns on assigning integer literals 0 and 1 to bool in C99 and later while preserving the existing C89 behavior.
 - funcArgNamesDifferentUnnamed warns on function declarations/definitions where a parameter in either location is unnamed
 - uninitMemberVarNoCtor warns on user-defined types where some but not all members requiring initialization have in-class initializers.
+- fcloseInLoopCondition warns when fclose() is used as a while loop condition, which may skip the loop body or double-close the file handle.
 
 C/C++ support:
 -

Original file line number	Diff line number	Diff line change
`@@ -8,6 +8,7 @@ New checks:`
`8`	`8`	`- MISRA C 2012 rule 10.3 now warns on assigning integer literals 0 and 1 to bool in C99 and later while preserving the existing C89 behavior.`
`9`	`9`	`- funcArgNamesDifferentUnnamed warns on function declarations/definitions where a parameter in either location is unnamed`
`10`	`10`	`- uninitMemberVarNoCtor warns on user-defined types where some but not all members requiring initialization have in-class initializers.`
	`11`	`+- fcloseInLoopCondition warns when fclose() is used as a while loop condition, which may skip the loop body or double-close the file handle.`
`11`	`12`
`12`	`13`	`C/C++ support:`
`13`	`14`	`-`