I am working on a large collaborative C ++ project that develops on various flavors of Linux, OS X and Windows And have to run. . We compile these platforms with GCC, Visual Studio C ++ and Intel C ++ compilers. As more and more people start to develop code for this project, we are starting to see strange errors in compilations and runtime, which are specific to special compilers on specific operating systems. An example of this is the underlying inclusion of headers that some OS / compiler pairs are looking for you, overloading a function from a base class in a crashing class.
My target is to compile on GCC hard and catch more errors in all platforms so that we can not run into these problems. Here is my list of flags about which I am trying for GCC which I have found through Google and the GCC Man pages:
- -Wall
- -Vuittra
- -Vinit-Self
- -Would-style-cast
- -Webloaded-Virtual
- -unified
- -Vinit-self
- -cissue
- -Pinky
In addition to PDT-error, which everyone has suggested, IMO, your compilation process Under the lint is always good to run.
There are some tools:
- (free)
Comments
Post a Comment