Re: [boost] [range] atl/mfc support

From: Daniel Walker (daniel.j.walker_at_[hidden])
Date: 2006-05-23 15:41:45

On 5/23/06, Thorsten Ottosen <thorsten.ottosen_at_[hidden]> wrote:
> Shunsuke Sogame wrote:
> > Daniel Walker wrote:
> >
> >>On 5/23/06, Shunsuke Sogame <mb2act_at_[hidden]> wrote:
> >>
> >>>BTW, I found a bug:
> >>>    <boost/range/concepts.hpp> seems to
> >>>    apply 'boost::size' to Forward Range.
> >>
> >>If I recall correctly applying boost::size() was intentional. size(r)
> >>is a valid expression for the ForwardRange concept,
>
> Well, that has changed.

I just read through the new documentation and size(r) is still a valid
expression of ForwardRange. I was looking at the new sections on
extending the library, and I'm a little confused. How do the free
standing functions for library extension, boost_range_size() and
boost::range_size() for example, relate to the range concepts? Before
I was talking about boost::size() calling std::distance to do the
work. Should it instead call these new functions?

Daniel Walker