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...@netlab.cs.rpi.edu]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html ]
> + 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