[Boost-docs] Padding for base64 dataflow iterators ?

Subject: [Boost-docs] Padding for base64 dataflow iterators ?
From: Timothy Madden (terminatorul_at_[hidden])
Date: 2010-07-28 11:40:24


Could the documentation page for dataflow iterators in the serialization
library please state that:

1. base64 iterators will /not/ add the padding '=' characters in the
encoded data, that are present in the canonical encoding in RFC4648 (The
Base16, Base32, and Base64 Data Encodings) ?

2. if your binary string to be encoded is not null-terminated, than the
iterators will not pad the input stream of bits with 0s to reach a
multiple of 6 bits


Just so the user knows she either has to ensure padding, or otherwise
she should not expect the resulting to exactly follow the RFC, as the
result might not be suitable for data interchange between applications,
etc ...

Or maybe the example could be changed to include padding, which would be
even better ... :)

Thank you,
Timothy Madden

This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:41 UTC