Re: STL, UTF8, and CodeCvt
"Philip" <Montrowe@Hotmail.com> wrote in message
news:1173210839.304892.253230@64g2000cwx.googlegroups.com...
PJ,
Thanks very much for the informative reply. It was exactly what I was
looking for.
I have some follow-up questions about standards committee noodlings...
On Mar 4, 2:44 pm, "P.J. Plauger" <p...@dinkumware.com> wrote:
Re: wstring
The wstring header described above has been proposed for the
next version of the C++ Standard.
It's a good-looking class. DOes it have a likelihood of getting onto
C0x?
I think so, yes.
Re: Narrow versus wide nomenclature
The committee is considering several approaches, but hasn't settled
on a given one yet.
Can you give me an idea of or point me to the proposals under
consideration?
I don't know how much of the mailings are visible to civilians
but you should find at least some information about work in
progress at:
http://www.open-std.org/jtc1/sc22/wg21/
Re: typealias versus typedef
That too is being discussed in the C++ committee.
Again, can you give me an idea of or point me to the proposals under
consideration?
As before.
Re: New Question
When and how will the standard support Unicode files on disks with
BOMs etc.
We have codecvt facets that handle a host of Unicode encodings,
with optional BOMs. It's too soon to tell whether something
like that will be mandated, but we stand ready with good
descriptions of the committee is interested.
Many thanks for the cogent and utterly on-topic reply
To others:
I am a little loose about STL versus the standard library and matters
like that so forgive the inaccuracies in my original post.
I still stick with my original idea that the widen and narrow function
nomenclature in the io-stream classes leaves no room for UTF-8 and
perhaps should be expanded (I see a great future for UTF-8). After
all that nomenclature is designed (I believe) to match the
differentiation between "external" and "internal" representations (see
Josuttis 14.4 p 720), which with the common advent of Unicode files on
disk is perhaps out-of-date.
So how about strungout/stringout for UTF-8? <grin>
C and C++ really deal with three types of character sequences:
1) single byte
2) multibyte
3) wide chararacters
There's much endemic confusion about what each of these mean, and
how they interact.
P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]