"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."

A number of open source packages ship with warnings-as-errors enabled by default in the build process... This can be EXTREMELY annoying, especially when it isn't easy to turn off...
Warnings can occur due to newer compilers, architecture/os differences etc, and in many cases warnings don't stop the program working. Sure in an ideal world code would all compile without any warnings on any platform, but in reality many warnings are false positives and noone writes perfect code.

Maybe you are right when talking about compiling third-party code you did not write but you are sure enough that it works, but for writing your own code, creating it with 0 warnings means two possitive things:

- You tried to keep your code quality as high as you could.
- You removed some unused variables and verified (and fix) some issues reported by the compiler that be potential errors right now or in the future.

I've been wondering about this myself. But I really hope it's not dead. Although I'm a Linux user 99.9% of the time, there is that rare instance where I've got to go to Windows to do something for which a Linux app doesn't exist. I recently had to retrieve a video file from a dash-cam that formats micro-SD cards in a proprietary format, and the only way to do it was to run a Windows application. That sucks, and the manufacturer (Abee) should be crucified for that, but it's these situations that make a market for ReactOS. If it was usable, I'd put it on a spare partition for those rare situations when it's needed.