Le 12 sept. 2010 à 18:46, Richard Frith-Macdonald a écrit :
On 12 Sep 2010, at 00:35, David Chisnall wrote:
I've now set up a jail that will check out the code each night and
run the static analyser. You can find the results here:
http://gnustep.theravensnest.org/
Currently only the link to the results for -base works - it's in
the process of generating the ones for -gui and -back.
Is there some way to mark things so that all the cases where the
analyser is known to be wrong (or is reporting something correctly,
but the 'problem' is actually intended behavior) will no longer be
reported?
It looks like there are so many false positives that it's hard to
use this report.
The annotations are documented here:
http://clang-analyzer.llvm.org/annotations.html
But the last time I tried to use them in several Étoilé frameworks, I
found them pretty limited, there was nothing to turn off the false
positives I had. It was six months ago, so I don't remember what they
were precisely. At least, I had false positives involving 'copy' in a
method name as David reported it.
Cheers,
Quentin.
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
