text
stringlengths
0
2.2M
// must actively #include each header to check for errors as simply testing
// '__has_include(<header>)' will give false positives in BSL_OVERRIDES_STD
// mode, finding our own intercept headers that simply forward to the
// original platform header, assuming it is available.
# include <memory_resource>
#endif
// ============================================================================
// TEST PLAN
// ----------------------------------------------------------------------------
// Overview
// --------
// This component provides macros that indicate the presence (or not) of
// selected features (i.e., header-files/types) in the native standard library
// used in the current build. In the current implementation, these flags are
// not set according to information directly from the library; rather, these
// features are inferred from platform and compiler information acquired from
// macros set in other components. The role of this test driver is to provide
// a redundant check that those macros were correctly combined to produce the
// expected results.
//
// Atypically of BDE test drivers, the semantic tests are done implicitly are
// the point of usage in client components. The test driver does a
// conditional, compile-time sanity check that the relevant header files can be
// included and, in some cases, that expected types are defined; however, there
// is also a *semantic* requirement associated with the macros defined in this
// component. The macros, when defined, imply that certain features
// files/types exist *and* that their implementation is sufficient to support
// certain uses in other (higher) components. The existence is tested by this
// test driver by minimal usage; however, comprehensive testing of the
// semantics is impractical.
//
// This test driver recognizes preprocessor flags that allow the developer to
// manually compile-time check for the absence of a feature when the associated
// macro test is *not* defined by the component. Note that the component does
// not require that feature be absent when the macro is undefined. See
// {'bsls_libraryfeatures'|Converse Logic}. These tests are provided as a
// debugging aid and as an investigative tool to discover the presence or
// absence of these features in libraries that have not yet been evaluated.
//
// The compilation of code that uses a feature can be forced by defining (e.g.,
// on the command line) a macro consisting of the feature macro suffixed by
// '_FORCE'. For example, to force a test for the presence of the '<tuple>'
// type specify '-DBSLS_LIBRARYFEATURES_HAS_CPP11_TUPLE_FORCE' on the command
// line. The code associated with that feature will be exposed to the compiler
// even if 'BSLS_LIBRARYFEATURES_HAS_CPP11_TUPLE_FORCE' was not defined by this
// component.
//
// Here, *failure* to compile this test driver is an indication that the
// feature is indeed absent from the library being evaluated. Should the test
// driver (unexpectedly) compile, run the test case in very very verbose mode
// to determine whether or not the macro for the feature of interest is
// defined.
//
//: o If defined, then component was correct in defining that macro (and any
//: expectation of compiler failure was incorrect).
//:
//: o If not defined, the component could be updated to recognize the build
//: configuration as providing the feature of interest.
//
// TBD Add tests for the new macros (and amendments to existing macros). See
// the macros without test-case numbers below.
// ----------------------------------------------------------------------------
// [ ] BSLS_LIBRARYFEATURES_HAS_C90_GETS
// [ ] BSLS_LIBRARYFEATURES_HAS_C99_FP_CLASSIFY
// [ 6] BSLS_LIBRARYFEATURES_HAS_C99_LIBRARY
// [ 6] BSLS_LIBRARYFEATURES_HAS_C99_SNPRINTF
// [ 1] BSLS_LIBRARYFEATURES_HAS_CPP98_AUTO_PTR
// [ 2] BSLS_LIBRARYFEATURES_HAS_CPP11_BASELINE_LIBRARY
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP11_EXCEPTION_HANDLING
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP11_GARBAGE_COLLECTION_API
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP11_MISCELLANEOUS_UTILITIES
// [ 3] BSLS_LIBRARYFEATURES_HAS_CPP11_PAIR_PIECEWISE_CONSTRUCTOR
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP11_PROGRAM_TERMINATION
// [12] BSLS_LIBRARYFEATURES_HAS_CPP11_RANGE_FUNCTIONS
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP11_STREAM_MOVE
// [ 4] BSLS_LIBRARYFEATURES_HAS_CPP11_TUPLE
// [ 5] BSLS_LIBRARYFEATURES_HAS_CPP11_UNIQUE_PTR
// [ 9] BSLS_LIBRARYFEATURES_HAS_CPP14_BASELINE_LIBRARY
// [11] BSLS_LIBRARYFEATURES_HAS_CPP14_INTEGER_SEQUENCE
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP14_RANGE_FUNCTIONS
// [14] BSLS_LIBRARYFEATURES_HAS_CPP17_BASELINE_LIBRARY
// [ ] BSLS_LIBRARYFEATURES_HAS_CPP17_BOOL_CONSTANT
// [ 8] BSLS_LIBRARYFEATURES_HAS_CPP17_PRECISE_BITWIDTH_ATOMICS
// [13] BSLS_LIBRARYFEATURES_HAS_CPP17_SEARCH_OVERLOAD
// [13] BSLS_LIBRARYFEATURES_HAS_CPP17_SEARCH_FUNCTORS
// [10] BSLS_LIBRARYFEATURES_STDCPP_GNU
// [10] BSLS_LIBRARYFEATURES_STDCPP_IBM
// [ ] BSLS_LIBRARYFEATURES_STDCPP_INTELLISENSE
// [10] BSLS_LIBRARYFEATURES_STDCPP_LLVM
// [10] BSLS_LIBRARYFEATURES_STDCPP_MSVC
// [10] BSLS_LIBRARYFEATURES_STDCPP_LIBCSTD
// [10] BSLS_LIBRARYFEATURES_STDCPP_STLPORT
// [ 7] int native_std::isblank(int);
// [ 7] bool native_std::isblank(char, const native_std::locale&);
// ----------------------------------------------------------------------------
// [14] USAGE EXAMPLE
// [-1] BSLS_LIBRARYFEATURES_HAS_CPP17_BOOL_CONSTANT: obsolescent: not defined
// ----------------------------------------------------------------------------