Enrico Granata c5bc412cf6 Synthetic values are now automatically enabled and active by default. SBValue is set up to always wrap a synthetic value when one is available. ... A new setting enable-synthetic-value is provided on the target to disable this behavior. There also is a new GetNonSyntheticValue() API call on SBValue to go back from synthetic to non-synthetic. There is no call to go from non-synthetic to synthetic. The test suite has been changed accordingly. Fallout from changes to type searching: an hack has to be played to make it possible to use maps that contain std::string due to the special name replacement operated by clang Fixing a test case that was using libstdcpp instead of libc++ - caught as a consequence of said changes to type searching llvm-svn: 153495		2012-03-27 02:35:13 +00:00
..
bitfield	Adding a new example of synthetic children provider	2012-03-17 02:02:03 +00:00
gnu_libstdcpp.py	Synthetic values are now automatically enabled and active by default. SBValue is set up to always wrap a synthetic value when one is available.	2012-03-27 02:35:13 +00:00
libcxx.py	Synthetic values are now automatically enabled and active by default. SBValue is set up to always wrap a synthetic value when one is available.	2012-03-27 02:35:13 +00:00