Boost logo

Boost :

Subject: Re: [boost] [string] proposal
From: Glyn Matthews (glyn.matthews_at_[hidden])
Date: 2011-01-21 07:42:57


Hello Matus,

On 21 January 2011 12:25, Matus Chochlik <chochlik_at_[hidden]> wrote:

> Dear list,
>
> following the whole string encoding discussion I would like
> to make some suggestions.
>
> >From the whole debate it is becoming clear, that
> instant switch from encoding-agnostic/platform-native
> std::string to UTF-8-encoded std::string is not likely
> to happen.
>
> <snip />

> /me ducks and covers :)
>
>
No need to duck and cover, you should be applauded for taking the initiative
here.

> The idea is that, let std::string/wstring be platform-specifically-
> -encoded as it is now, but also let the boost::string handle
> the conversions as transparently as possible so if in
> case the standard adopts it, std::string would become
> a synonym for boost::string.
>
>
This is *very* promising.

> It is only partially implemented and there are two examples
> showing how things could work, but the real UTF-8 validation,
> transcoding, error handling, is of course missing. Remember
> it is aimed at the design of the interfaces at this point.

> If you have the time, have a look and if my suggestions
> and/or the code looks completely wrong, please, feel free
> to slash it to pieces :), and if you feel up to it, propose
> something better.
>
> If this or something completely different and much better
> that comes out of it, will be agreed upon, we could set up
> a dedicated git repository for Boost.String and maybe try if
> the new suggested collaborative development in
> per-boost-component repositories really works. :)
> If some of the people that are skilled with unicode
> would join or lead the effort it would be awesome.
>
>
Definitely make a Git repository.

Regards,
Glyn


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk