Use new method for specifying custom rules
Support GCC's Conditionals with Omitted Operands.

There is a GCC extension which allows the middle operand in a conditional
expression to be omitted. Therefore, the expression "x ? : y" has the value of x
if that is nonzero; otherwise, the value of y.
Support variadic macros.
Merge pull request #137 from Typz/variadic_macros

Support variadic macros.
Merge pull request #138 from Typz/gcc_ternary

Extension: GCC's conditionals with omitted operands.
Support GCC's Conditionals with Omitted Operands #138
Mark the rule change as extension
enable multi language analsysis

Signed-off-by: Jorge Costa <jorge.costa@tekla.com>
Small refactoring: inline CxxPlugin:isEnabled()
Fix file ending.

Files got commited to Git with CRLF (windows) file ending, causing issues on
linux.
Merge pull request #141 from Typz/crlf

Files got commited to Git with CRLF (windows) file ending, causing issues on
linux.
add header file to mock up Visual Studio 2010 specific extensions to C++
handle error recovery on global declaration level: skip syntax errors and proceed with next declaration
add switch sonar.cxx.errorRecoveryEnabled=true/false
add syntax error logging
add a rule to report on every recoveredDeclaration (C++ skip parser error)
Merge pull request #140 from guwirth/enhancement/error-recovery-declaration

Enhancement/error recovery declaration
Merge branch 'feature/deprecate-extensions-rules' of git://github.com/jmecosta/sonar-cxx into jmecosta-feature/deprecate-extensions-rules

Conflicts:
	sonar-cxx-plugin/src/test/java/org/sonar/plugins/cxx/cppcheck/CxxCppCheckRuleRepositoryTest.java
Reenable a test disabled in the last merge (?)
Merge pull request #142 from guwirth/enhancement/visual-studio-macros

add header file to mock up Visual Studio 2010 specific extensions to C++
Support parsing GCC build log.

The sonar.cxx.compiler.parser property can be used to select either vc (default)
or gcc build log parser.
Support GCC's statement expression.
Fix reserved name check.

* According to the standard, reserved names that either begin with underscore
followed by a capital letter and a capital letter, contain 2 consecutive
underscores, or are part of the reserved keywords.
* The check was not working for function-like macros.
* The check could report errors if #define is used in commnets.
Fix correct include check if comment is right after file string.

The checker was incorrectly reporting issues if the name is specified in quotes,
and followed immediately (no space) by a comment.