Implementing SMP on a UTF-16 OS

[Peter Constable]

I’m no expert on driver development, but Max’s comments got me curious.

“Windows Driver Kit (WDK) 10 is integrated with Microsoft Visual Studio 2015…”
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557573(v=vs.85).aspx


“In Visual Studio 2015, the C++ compiler and standard library have been updated with enhanced support for C++11 and initial support for certain C++14 features. They also include preliminary support for certain features expected to be in the C++17 standard.”
https://msdn.microsoft.com/en-us/library/hh409293.aspx



From: Unicode [mailto:unicode-bounces at unicode.org] On Behalf Of Max Truxa
Sent: Monday, August 10, 2015 11:27 PM
To: Marcel Schneider <charupdate at orange.fr>
Cc: Unicode Mailing List <unicode at unicode.org>
Subject: Re: Implementing SMP on a UTF-16 OS


On Aug 10, 2015 10:53 PM, "Marcel Schneider" <charupdate at orange.fr<mailto:charupdate at orange.fr>> wrote:
>
> This is clearly a Unicode implementation problem. C and C++ should be standardized for handling of UTF-16. IMO we cannot consider that Windows supports UTF-16 for internal use, if it does not support surrogates pairs except with workarounds using ligatures.

C and C++ *are* "standardized for handling of UTF-16"... and UTF-8... and UTF-32.
If you are interested in this topic just search for "C++ Unicode string literals" and "C++ Unicode character literals" which are standardized since C11/C++11 (with the exception of UTF-8 character literals which will follow in C++11; don't know about C though).
The reason you won't be able to easily use these features is because the compiler shipping with the WDK is still only supporting C89/C90. And sadly for us driver developers Microsoft will not change this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20150812/94993ce1/attachment.html>