From -5848539585668286545
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,ae3be6396bd7be12
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 1994-08-07 13:24:03 PST
Newsgroups: comp.std.c++
Path: bga.com!news.sprintlink.net!news.onramp.net!convex!cs.utexas.edu!swrinde!howland.reston.ans.net!agate!msuinfo!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!news
From: maxtal@physics.su.OZ.AU (John Max Skaller)
Subject: Re: Standard C++ String classes
Message-ID: <Cu6K8B.B9G@ucc.su.OZ.AU>
Sender: news@ucc.su.OZ.AU
Nntp-Posting-Host: physics.su.oz.au
Organization: School of Physics, University of Sydney, Australia
References: <31865v$sq8@silver.jba.co.uk> <CtozHx.9JH@ucc.su.OZ.AU> <31j66g$gik@silver.jba.co.uk>
Date: Sun, 7 Aug 1994 19:45:47 GMT
Lines: 40

In article <31j66g$gik@silver.jba.co.uk> "Jonathan de Boyne Pollard" <@jba.co.uk:JdeBP@osmium> writes:
>
>>>1.2   If embedded NULs are allowed and the string length takes
>>>      account of them, what are the semantics of 
>>>      string::operator const char * ?
>>
>>	Returns a pointer to an array containing the string.
>
>NUL terminated, or not ?  I've also been told that there will be no
>such operator as standard and that there will be a char * c_str(void)
>member instead.

	You are correct, although the name got changed recently
to "data". It might get changed back. And, a nul is appended
to the bytes of the string so you can use it like an asciiz
string provided it has no embedded nuls.
>
>>	.. And the reason is at least part that ISO REQUIRES
>>that new languages NOT treat any character specially, in particular
>>because some ISO Standard multibyte character sequences contain
>>NUL (0) valued characters.
>
>So the standard string class will handle multibyte characters instead of 
>this being in an additional class ?

	There will be a string of wchar_t as well. 
Multibyte character handling will probably be done
by the iostream subsystem.
>
>Is the differentiation between ASCIIZ strings and multibyte strings in C++ 
>"going away" then ?
>
	Internally, for international characters, use wchar_t strings.
I guess you can write your own handlers.

--
        JOHN (MAX) SKALLER,         INTERNET:maxtal@suphys.physics.su.oz.au
	Maxtal Pty Ltd,		    
        81A Glebe Point Rd, GLEBE   Mem: SA IT/9/22,SC22/WG21 
        NSW 2037, AUSTRALIA	    Phone: 61-2-566-2189


