Re: [boost] Is Boost.Range broken?

Subject: Re: [boost] Is Boost.Range broken?
From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2008-11-23 08:07:16

Tomas Puverle skrev:

> My proposed fix would be the following:
> 
> Roll back iterator_range to the pre-1.35 release state immediately.
> 
> For a future release, create a new class, boost::simple_range which has the
> behaviour of the new version (i.e. no singular member).  Publicly derive
> iterator_range from simple_range and provide additional factory functions such
> as make_simple_range().
> 
> I would appreciate any feedback on this issue.

I think going backwards is not possible. A components performance can be 
just as important to some people as stability of interface can be to others.

We could introduce boost::range<iterator> with the old behavior, 
deriving from boost::iterator_range<iterator>. In this case, I need
someone to submit code and tests and documentation (I'm way to busy to 
do that).

-Thorsten