Subject: Re: [boost] [general] What will string handling in C++ look like in the future [was Always treat ... ]
From: Patrick Horgan (phorgan1_at_[hidden])
Date: 2011-01-19 23:38:43
On 01/19/2011 08:51 AM, Mathias Gaunard wrote:
> ... elision by patrick ...
> *Scenario D:*
> Use Ranges, don't care whether it's std::string, whatever_string, etc.
> This also allows maximum efficiency, with lazy concatenation,
> transformations, conversion, filtering etc.
> My Unicode library works with arbitrary ranges, and you can adapt a
> range in an encoding into a range in another encoding.
> This can be used to lazily perform encoding conversion as the range is
> iterated; such conversions may even be pipelined.
Sounds interesting. Of courses ranges could be used with strings of
whatever sort. Is the intelligence about the encoding in the ranges?
As you iterate a range does it move byte by byte character by character,
does it deal with compositions? Is it available to read?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk