Added a philosophy.md document.

philosophy.md

@@ -0,0 +1,53 @@
+
+Cppcheck Philosophy
+===================
+
+It is important that everybody in the Cppcheck team has a consistent idea about how this tool should work.
+
+This is a static analyser tool. When it comes to writing warnings, quality is much more important than quantity.
+
+
+No false positives
+------------------
+
+A fundamental goal is "no false positives".
+
+It is not possible to achieve "no false positives" completely. One case where false positives are OK is when the code is garbage.
+
+If the code is written as it is by design, then our goal is to not warn.
+
+If it is not known if there is a problem, then in general we need to bailout. We can only warn when we see that there is a problem.
+
+Stylistic checks are much more prone to false positives and therefore we should avoid writing stylistic checks mostly.
+
+
+No configuration
+----------------
+
+We want that a user can run Cppcheck without explicit -D and -I configuration.
+
+When this happens the false positives should be avoided. The user can reduce false negatives with configuration.
+
+
+Allow compiler extensions
+-------------------------
+
+This is not just a tool for mainstream gcc/msvc c/c++ developers. If you can compile the code with a C/C++ compiler then our goal is that Cppcheck can check it.
+
+
+C++ language
+------------
+
+Our goal is to be highly portable. Users must be able to compile Cppcheck with GCC 4.6 or MSVS 2013.
+
+No C++14 is allowed. A subset of the C++11 is allowed.
+
+
+No dependencies
+---------------
+
+We are very careful about dependencies.
+
+
+
+