24 Jul
2017
24 Jul
'17
3:35 p.m.
On 07/24/17 18:24, Greger via Boost wrote:
Here is some documentation:
The interface documented there does not account for the possibility that the original data may not be a string (of characters). My requirements to a Base64 libraries would be: - The library should be able to work with any binary data. - It should be able to produce encoded/decoded data in a user-supplied storage. - I would like to be able to supply custom character conversion rules and possibly disable trailing padding so that different variants of Base64 (e.g. [1]) can be implemented. - The library should be fast. [1]: https://tools.ietf.org/html/rfc4648#section-5