Topic: Should C++0x contain distinct type for UTF-8?
Author: "Martin B." <0xCDCDCDCD@gmx.at>
Date: Sat, 31 Jul 2010 13:16:46 CST Raw View
Hi all!
Current draft N3092 specifies:
+ char16_t* for UTF-16
+ char32_t* for UTF-32
+ char* for execution narrow-character set
+ wchar_t* for execution wide-character set
+ unsigned char* for ... yes, for what?
Wouldn't it make sense to have a char8_t where char8_t arrays would
hold UTF-8 character sequences exclusively?
What is the rational for not including it?
cheers,
Martin
--
[ comp.std.c++ is moderated. To submit articles, try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html ]
Author: =?iso-8859-2?B?SmFuIFJpbmdvuQ==?= <tringi@mx-3.cz>
Date: Sun, 1 Aug 2010 14:47:31 CST Raw View
Dne Sat, 31 Jul 2010 21:16:46 +0200 Martin B. <0xCDCDCDCD@gmx.at> napsal/-a:
> + unsigned char* for ... yes, for what?
Raw data buffers (bytes), what else?
And maybe pointer to small number(s) fitting in 0-255 range :)
--
Jan Ringo
www.ringos.cz
--
[ comp.std.c++ is moderated. To submit articles, try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html ]