|
From: Lewis H. <hen...@op...> - 2016-07-20 20:04:35
|
Hi Markus,
Just a quick question – what about Microsoft Visual Studio? I’ve been using 2010 (since it’s been stable for a while), but it doesn’t support the full C++11 standard, particularly char16_t. I don’t know about 2012 or 2015.
Lewis Henderson
From: Markus Scherer [mailto:mar...@gm...]
Sent: Wednesday, July 20, 2016 3:58 PM
To: icu-design <icu...@li...>; ICU support mailing list <icu...@li...>
Subject: [icu-support] ICU4C proposal to use C++11 in ICU 58
Dear ICU team & users,
We have finally decided to use C++11 features in the ICU implementation, at least as far as they are widely supported<https://urldefense.proofpoint.com/v2/url?u=http-3A__en.cppreference.com_w_cpp_compiler-5Fsupport&d=CwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=yAhF6NGJ7EPmZkvswZOswwnYxaueKkO53V282tTn1P4&m=zquc6d9VqGWTPtiizSj6kFu5C7RRHMsZrQbkOEI-Ri8&s=zz4xlkNaDl9C3lpeAJnv5tKjkFbcehb20DRrbSdXyDI&e=> in modern versions of compilers (excluding “Digital Mars C++” aka Zortech C++/Symantec C++). This means that ICU4C will have to be compiled with a compiler that supports C++11, and configured to do so.
We also propose to use C++11 in public ICU header files, for example using constexpr, override, deleted functions, and noexcept. This means that applications which call ICU4C C++ APIs will also have to be compiled with C++11. It should have no effect on applications which call only C APIs.
Please let us know right away if you have strong concerns about using C++11 in public ICU header files.
Sincerely,
markus
http://bugs.icu-project.org/trac/ticket/12643<https://urldefense.proofpoint.com/v2/url?u=http-3A__bugs.icu-2Dproject.org_trac_ticket_12643&d=CwMFaQ&c=ZgVRmm3mf2P1-XDAyDsu4A&r=yAhF6NGJ7EPmZkvswZOswwnYxaueKkO53V282tTn1P4&m=zquc6d9VqGWTPtiizSj6kFu5C7RRHMsZrQbkOEI-Ri8&s=C2vPzWYu1v5BFDHDZf7YeSYxnDL1YiKkvPeBOv5wzxU&e=> "ICU4C 58 using C++11"
|