From: Pavol Droba (droba_at_[hidden])
Date: 2004-04-14 06:37:26
On Wed, Apr 14, 2004 at 02:26:34PM +0400, Vladimir Prus wrote:
> Pavol Droba wrote:
>
> >> Hmm... shouldn't it be the other way around? That is
> >> boost::unicode_string should provide some iterators which can be passed
> >> to the string_algo library, and guarantee that it works OK.
> >>
> > AFAIK there is no unicode_string there so far. So the string_algo lib
> > works with the stuff, that is available. i.e. std containers (with
> > fixed-width characters) and locales.
> >
> > I can imagine a support for unicode string. If it would be well designed,
> > many string algorithms can work almost out-of-box.
>
> I mean that one of the design goals of unicode string is allowing other code
> (like string_algo) to work out of the box.
>
I understand that, but there is a conceptual difference between classic strings and
unicode string. For instance to make to_upper algorithm, former one needs locales,
while the second one has toupper functionality inbound.
I can imagine a way how to make these two compatible, question is however if it
won't compromise natural properties of specific string representations.
Pavol