Re: [boost] base64?

On Mon, Jul 24, 2017 at 9:54 AM, Roger Leigh via Boost wrote:

...

We already have base64 conversion in boost/archive/iterators/*base64*.hpp. It works but screws up the whitespace (https://stackoverflow.com/questions/10521581/base64-encode-using-boost-throw...). It's a shame the various adapters don't work properly together; is there any prospect of this being fixed, or is the existing design simply too inflexible to make a proper base64 implementation? I think a good base64 implementation would be an excellent subject for GSoC or someone who wants to participate in Boost we would just have to clearly define the things we want from it:

* Caller provided buffers * Allocator awareness * Flexible types of input * Choice of alphabet * Choice of radix? * Option for line-widths / newlines * Iterator based interface * Variations such as rfc3548, rfc, 4648, modified Base64 for URL

Could be called Boost.Radix

I know such a library would be immensely useful to a higher-level library which tries to address some of those "out-of-scope" items in Beast. Base-64 and other radix encodings come up often in HTTP field values and uri targets, as well as in the body of certain message types.

If anyone is interested I wouldn't mind getting together on Google Hangouts with a https://kobra.io/#/ shared document and hammering out a prototype set of declarations, which someone else could implement.

Thanks

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost I don't really know what to say. The lib was created (perhaps) 7-8 years ago when I needed C/C++ functions to do the job with the requirement to be compatible to PHP's corresponding routines. And the version I have now does exactly that. It has not been 'released' ever. What conserns

On 24.07.2017 20:02, Vinnie Falco via Boost wrote: license then I'm not a lawyer, money is funny but not strictly a requirement. Considering that the lib was created on a debian linux workstation using open source tools, then it should probably be open source as well. Greg