Denis Shevchenko wrote:
Hi all!
Not so long ago I was looking for a solution to Base64 encoding/decoding. In this page - http://www.boost.org/doc/libs/1_46_1/libs/serialization/doc/dataflow.html - I found example of such solution, with 'base64_from_binary' and 'transform_width' iteartors. But it is just a "blank", not ready-to-use solution.
Hmmm - I'm not sure what this means. It is used in serialization library so it's not just a "blank". Perhaps you're refering to the way it's implemented by building up from more primitive concepts using concepts now implemented are part of the range library. It predates the range library but it seems to me it's very similar. I find the way it's implemented very appealing. For example, if one wanted to change the line length, this would be easy to do without adding anything. The base64 implementation in the serialization library isn't really a library, but more of an instance of a huge family of text processing facilities. So I think a much more interesting and useful project would be: "an optimally fast, character range processing library which can be used construct a wide variety of character processing algorithms by composition of more primitive concepts in a regular way." Examples include base64, ... and generation of custom code_convert facets for io_streams.. Robert Ramey