Boost C++ Libraries: Ticket #8369: Do not compile even trivial UTF16 and UTF32 tests with libc++

Marshall Clow — Tue, 02 Apr 2013 15:27:47 GMT

Additional information:

The C++ standard (I looked at n3216) specifies (in 22.3.1.1.1) that numpunct<char> and numpunct<wchar_t> are required, and does not mention numpunct<char16_t> or numpunct<char32_t> at all.

gcc (I checked version 4.8) provides a completely templated implementation of std::numpunct, so it supports specializing on any character type. libc++ provides two implementations: one for char and the other for wchar_t.

Antony Polukhin — Tue, 02 Apr 2013 19:56:52 GMT

(In [83717]) Disable UTF16 and UTF32 tests for libc++ (refs #8369)

Antony Polukhin — Tue, 02 Apr 2013 19:57:38 GMT

Replying to marshall:

Additional information:

The C++ standard (I looked at n3216) specifies (in 22.3.1.1.1) that numpunct<char> and numpunct<wchar_t> are required, and does not mention numpunct<char16_t> or numpunct<char32_t> at all.

Yes, they are not required, which makes a lot of troubles when std::basic_istream and std::basic_ostream classes are used with those character types as template parameters (users miss this functionality, see 1, 2).

gcc (I checked version 4.8) provides a completely templated implementation of std::numpunct, so it supports specializing on any character type. libc++ provides two implementations: one for char and the other for wchar_t.

GCC-4.7 was also providing a fully templated version. Unfortunately, some support from glibc was required, so usage of std::numpunct<char16_t> was leading to segmentation faults (though have not checked it for a year, may be things changed).

status changed; resolution set

Antony Polukhin — Thu, 04 Apr 2013 15:47:05 GMT

status new → closed
resolution → fixed

(In [83764]) Mrege from trunk:

Disable UTF16 and UTF32 tests for libc++ (fixes #8369)