it doesn't do the padding with '=' Much worse is that it doesn't parse input with such padding correctly. This issue is so severe that IMO that thing should not be called base64, as it misleads new users.
As to the original post, having a good base64 implementation in boost would
be great.
пн, 15 мая 2017 г., 17:25 Robert Ramey via Boost
On 5/15/17 1:11 AM, Gavin Lambert via Boost wrote:
On 15/05/2017 19:18, Olaf van der Spek wrote:
On Sun, May 14, 2017 at 8:15 AM, Greger wrote:
Second:is there any interest in base64? I have a library for encoding and decoding, which I could contribute.
I think it'd be nice to have, I've needed it before.
According to this, Boost already has the parts, albeit possibly a bit hidden away:
http://stackoverflow.com/questions/7053538/how-do-i-encode-a-string-to-base6...
Indeed, if one just googles boost base64 he'll find a large number of hits on pages which explain how to do this using the component in the serialization library. The only issue with the one in the serialization library is that as it stands, it doesn't do the padding with '=' because the serialization library doesn't need it. But the posts alluded to above demonstrate how to add this.
The serialization component which deals this is called "dataflow iterators" and the base64 component is just single usage case of this approach.
Robert Ramey
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost