boostorg/config
1
0
Fork 1
mirror of https://github.com/boostorg/config.git synced 2025-07-30 04:17:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

don't define BOOST_DATE_TIME_NO_LOCALE in Boost.Config header

Browse Source
This commit is contained in:
Paul Groke
2017-02-26 15:31:38 +01:00
parent 6a89b24eed
commit 934c372112
1 changed files with 0 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
include/boost/config/stdlib/xlcpp_zos.hpp
View File

@ -23,15 +23,6 @@
#define BOOST_HAS_MACRO_USE_FACET
// Unfortunately the IBM z/OS XL C/C++ standard library has a bug when it comes to locales...
// The locale-enabled overloads of functions like std::isdigit or std::tolower in <locale> are defined in a nested namespace and pulled into "std" via "using namespace xyz;".
// The classic C versions of those functions are defined in the global namespace, and then pulled into "std" via "using ::functionname;" in <cctype>.
// This causes problems when including both <locale> and <cctype>, because the compiler will stop looking after it finds a function that was pulled in via "using ::functionname;"
// (which is correct behavior as far as the compiler is concerned).
// I.e. you cannot call a locale-enabled overload of one of those functions if both <locale> and <cctype> were included.
// To deal with this we have to define at least BOOST_DATE_TIME_NO_LOCALE (possibly others?), even though there - theoretically - *is* support for locales.
#define BOOST_DATE_TIME_NO_LOCALE
#define BOOST_NO_CXX11_HDR_TYPE_TRAITS
#define BOOST_NO_CXX11_HDR_INITIALIZER_LIST