Fixup #14303: Function pointers are not known to be 1

[chrchr-github]

The auto variable in the TODO has no ValueType.

[dmcppcheck]

Test results for commit 1556569 (tools/test-my-pr.py, main compared to this PR):

Test: http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/pr-8919/
packages: 1000
Differing warnings: 44 (+14 -30)
AI review: 10 improvement, 25 neutral, 6 regression, 3 unclear (http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/pr-8919/2026-10-05_16-52-33-1556569a078c-review.txt)
Timing: +0.5% (http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/pr-8919/2026-10-05_16-52-33-1556569a078c_timing.html)

_{Posted automatically by the cppcheck PR test runner. +N: warnings only with this PR, -N: warnings only with main. The AI review is written by Claude and can be wrong.}

[dmcppcheck]

@claude review

[claude]

Reviewed the change. Limiting the function-name inference to isUsedAsBool contexts fixes the bug: before this change, g in g() or x = g got a known value of 1, and that value then propagated to function-pointer variables. I found no correctness issues. isUsedAsBool is only extended for ==|!= against a known 0, so it shouldn't add false positives in other callers.

Notes:

• This regresses auto q = g; if (q == nullptr) (now a TODO). A follow-up could set an impossible 0 value, rather than a known 1, on function-name tokens in any non-call context. That would let the value flow forward to q without bringing the original bug back.
• Minor test gap: the new valueflow test only covers the declared-pointer case. A check that x in auto x = g; return x(); doesn't get a known value of 1 would also guard the auto path.

🤖 Generated with Claude Code

[danmar]

Please check the test results. If you feel satisfied then feel free to merge.