unique_ptr is probably useable. The library is only a problem when you need something that involves constexpr. constexpr support has been disabled in the library because some constexpr code uses C floating point functions that weren¹t changed to allow their use in constexpr C++ functions.
Disabling constexpr can cause problems with other C++11 functionality as we discovered with std::atomic. Initialization order of static atomics was incorrect because constructors in the atomics classes weren't constexpr. A constexpr related problem with unique_ptr seems...unlikely. QNX 7.0 is currently early 2017. (2H is incorrect if 2H == second half) ----- Original Message ----- On 2016-02-26, 2:15 PM, "Development on behalf of Blasche Alexander" <[email protected] on behalf of [email protected]> wrote: > >> -----Original Message----- >> From Marc Mutz >> On Friday 19 February 2016 22:01:02 Knoll Lars wrote: >> > * We continue to support QNX 6.6 >> >> Does someone here know (Rafael) when we can expect a QNX that supports >> C++11 >> at the library level? > >During Embedded World, a person at the QNX booth told me that QNX 7.0 is >what will fix this gap. Please don't nail me down on the timeline but I >believe it was 2H 2017 (2017 for sure). > >-- >Alex >_______________________________________________ >Development mailing list >[email protected] >http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
