Tor Arne Vestbø c3bd5ffdc8 Don't wrap feature detection macros with QT_HAS_FOO() variants ... Using wrappers for these macros is problematic when for example passing the -frewrite-includes flag to preprocess sources before shipping off to distcc or Icecream. It will also start producing warnings when compilers implement http://eel.is/c++draft/cpp.cond#7.sentence-2. See for example https://reviews.llvm.org/D49091 Both https://clang.llvm.org/docs/LanguageExtensions.html and the SD-6 document at https://isocpp.org/std/standing-documents/sd-6-sg10-feature-test-recommendations recommend defining '__has_foo(x) 0' as a fallback for compilers without the macros, so that's what we go for. Change-Id: I0298cd3b4a6ff6618821e34642a5ddd6728be767 Reviewed-by: Alex Richardson <arichardson.kde@gmail.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2019-12-10 00:48:07 +01:00
..
.gitignore	Add a test for container API symmetry	2017-04-07 08:32:24 +00:00
containerapisymmetry.pro	Introduce QT_NO_LINKED_LIST and mark QtBase (almost) free of it	2019-07-12 14:26:30 +02:00
tst_containerapisymmetry.cpp	Don't wrap feature detection macros with QT_HAS_FOO() variants	2019-12-10 00:48:07 +01:00