Re: [boost] Is Boost interested in the Boost-based Base64 library

Subject: Re: [boost] Is Boost interested in the Boost-based Base64 library
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2011-06-09 15:21:46

Denis Shevchenko wrote:
> Rob Stewart wrote:
>
> > That interface is restrictive.  Why not take iterators and
> > ranges for input and output iterators for output.  That
> > would grant greater flexibility to source and destination:
> > your code would be captured as algorithms.
>
> Yes, Rob, iterators are more flexible, but this flexibility is
> not always necessary.
>
> For example, we can write:
>
> std::vector< int > v{ 1, 2, 3 };
> auto it = std::find( v.begin(), v.end(), 2 );
>
> But Boost.Range provides "less flexible" solution:
>
> std::vector< int > v{ 1, 2, 3 };
> auto it = boost::range::find( v, 2 );
>
> IMO, this solution is much easier and safer, but less flexible.

Since I suggested iterators and ranges as the interface, and your examples implied neither, I fail to understand how your answer actually bears on my suggestion.  Does your interface support ranges without your having shown it?  Is there output iterator support?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer                     using std::disclaimer;
Dev Tools & Components
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.