Edwin Vane c383960be9 Don't replace macro usage if macro body has NULL ... In case of macro body expansion, check to see if the macro is named NULL and don't replace inside the macro body. This fixes the case when NULL appears inside the macro body and the transform replaces the usage of the macro with nullptr. This is an easy fix for the problem for now and we should analyze the macro body to see if it expands to only NullToPointer in the future for a more robust solution that takes care of user defined macros that behaves like NULL. Other changes: - Moved complex macro tests to macros.cpp - Added new test cases. - Added checks to make sure that the macro bodies are not modified by the tool. Fixes: PR15396 Author: Tareq A Siraj <tareq.a.siraj@intel.com> llvm-svn: 177422		2013-03-19 18:47:03 +00:00
..
NullptrActions.cpp	Don't replace macro usage if macro body has NULL	2013-03-19 18:47:03 +00:00
NullptrActions.h	Add use-nullptr transform to cpp11-migrate	2013-01-22 18:31:49 +00:00
NullptrMatchers.cpp	Prevent nullptr_t-typed exprs from being replaced	2013-03-15 18:10:07 +00:00
NullptrMatchers.h	Add use-nullptr transform to cpp11-migrate	2013-01-22 18:31:49 +00:00
UseNullptr.cpp	Added summary option to cpp11-migrate tool	2013-03-05 00:12:33 +00:00
UseNullptr.h	Added summary option to cpp11-migrate tool	2013-03-05 00:12:33 +00:00