Linked by Thom Holwerda on Tue 2nd Apr 2013 12:23 UTC
ReactOS "The ReactOS project is rapidly developing. One of the developers participating in this project suggested that we re-analyzed the source code, as the code base is growing fast. We were glad to do that. We like this project, and we'll be happy if this article helps the developers to eliminate some bugs. Analysis was performed with the PVS-Studio 5.02 code analyzer."
Thread beginning with comment 557347
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Advert?
by ebasconp on Tue 2nd Apr 2013 16:53 UTC in reply to "RE: Advert?"
Member since:


Advertising or not, I would like to see more static code analysis for more open source projects.

It is good advertising for the product, good advertising for the open source projects and makes you think: "Hey! I can help right there!" ;)

Reply Parent Score: 3

RE[3]: Advert?
by Valhalla on Tue 2nd Apr 2013 17:09 in reply to "RE[2]: Advert?"
Valhalla Member since:

Yep, apart from possibly having to wade through 'false positives' there's really no downside to running your codebase through a static analyzer.

I know Haiku has used Coverity and as I recall so had ReactOS before this aswell.

Reply Parent Score: 2

RE[4]: Advert?
by moondevil on Tue 2nd Apr 2013 20:37 in reply to "RE[3]: Advert?"
moondevil Member since:

I usually advocate to always enable warnings as errors and use a syntactic analyzer in the continuous build server, specially in languages where it is so easy to write insecure code.

Locally a developer can do whatever s/he wants, but into source control, only sane content gets in.

Reply Parent Score: 2