Closed hacketiwack closed 1 month ago
Thanks, I've gone through them, and I think there was one actual bug, which is the boolean value assigned to a pointer. Then there was a missing include, which I also fixed.
The scan-build records are all about assigning values to variables without reading from them. While it's obviously superfluous, it can make sense on order for the code to be consistent. I suggest you disable that check as it is in the Github action workflow.
While I was playing around with the
cppcheck
andscan-build
commands, I came across a few "issues" in the code. As I'm not a C programmer, these issues might not be real issues.Hereafter is the result of the
cppcheck --force
command:The result of the command
scan-build
is a bit more verbose and is available here.