Pour obtenir une clé
d'essai remplissez le formulaire ci-dessous
Demandez des tariffs
Nouvelle licence
Renouvellement de licence
--Sélectionnez la devise--
USD
EUR
RUB
* En cliquant sur ce bouton, vous acceptez notre politique de confidentialité

Free PVS-Studio license for Microsoft MVP specialists
To get the licence for your open-source project, please fill out this form
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

I am interested to try it on the platforms:
** En cliquant sur ce bouton, vous acceptez notre politique de confidentialité.

Votre message a été envoyé.

Nous vous répondrons à


Si vous n'avez toujours pas reçu de réponse, vérifiez votre dossier
Spam/Junk et cliquez sur le bouton "Not Spam".
De cette façon, vous ne manquerez la réponse de notre équipe.

>
>
Should I fix all the errors found by th…

Should I fix all the errors found by the static code analyzer?

05 Avr 2013
Author:

When analyzing larger projects static code analyzers usually generate a lot of error messages or warnings. And choosing whether all these errors should be fixed largely depends on current stage of project life cycle.

If project is being actively developed it makes a lot of sense to fix as many errors as possible - Quality Assurance did not yet spend time to detect these bugs. And when we are saving time we are actually reducing project cost.

When

But any static code analyzer always generates many so called "false-positive alarms" besides useful messages.

Various static analyzers treat this problem in different ways. Some analyzers ignore those suspicious fragments in code where the probability of an error is far from 100%. But most analyzers use an opposite approach, i.e. they generate much more "false alarms", however the risk that you might miss real error messages is much lower.

Since analysis results often contain a lot of such "false-positive" messages, there is no sense in correcting all the places in your code marked by the analyzer. However, developers must look through all the warnings anyway and configure the analyzer for each particular project eliminating such low-priority messages and focusing on detecting more serious issues.

References

Comments (0)

Next comments
Unicorn with delicious cookie
Nous utilisons des cookies pour améliorer votre expérience de navigation. En savoir plus
Accepter