Skip to content
Snippets Groups Projects
Commit 8502b7dc authored by Nat Goodspeed's avatar Nat Goodspeed
Browse files

DRTVWR-418: Work around VS2013's lack of __has_feature().

parent ccc42830
No related branches found
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
indra/llcommon/llinstancetracker.h
+ 8
− 1
View file @ 8502b7dc
...@@ -36,7 +36,14 @@ ...@@ -36,7 +36,14 @@
#include <boost/iterator/indirect_iterator.hpp> #include <boost/iterator/indirect_iterator.hpp>
// As of 2017-05-06, as far as nat knows, only clang supports __has_feature(). // As of 2017-05-06, as far as nat knows, only clang supports __has_feature().
#if defined(LL_TEST_llinstancetracker) && defined(__clang__) && __has_feature(cxx_noexcept) // Unfortunately VS2013's preprocessor shortcut logic doesn't prevent it from
// producing (fatal) warnings for defined(__clang__) && __has_feature(...).
// Have to work around that.
#if ! defined(__clang__)
#define __has_feature(x) 0
#endif // __clang__
#if defined(LL_TEST_llinstancetracker) && __has_feature(cxx_noexcept)
// ~LLInstanceTracker() performs llassert_always() validation. That's fine in // ~LLInstanceTracker() performs llassert_always() validation. That's fine in
// production code, since the llassert_always() is implemented as an LL_ERRS // production code, since the llassert_always() is implemented as an LL_ERRS
// message, which will crash-with-message. In our integration test executable, // message, which will crash-with-message. In our integration test executable,
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment