----- Original Message ----- From: "vicente.botet" <vicente.botet@wanadoo.fr> To: <boost@lists.boost.org> Sent: Wednesday, April 28, 2010 11:05 PM Subject: Re: [boost] [range] Permission to merge extensivedocumentationworkfrom trunk.

----- Original Message ----- From: "vicente.botet" <vicente.botet@wanadoo.fr> To: <boost@lists.boost.org> Sent: Wednesday, April 28, 2010 11:03 PM Subject: Re: [boost] [range] Permission to merge extensive documentationworkfrom trunk.

...

----- Original Message ----- From: "Neil Groves" <neil@grovescomputing.com> To: "Boost mailing list" <boost@lists.boost.org> Sent: Wednesday, April 28, 2010 9:35 PM Subject: [boost] [range] Permission to merge extensive documentation workfrom trunk.

...

Please may I merge just the documentation changes that have been performed on the trunk?

These include: 1. corrections to documentation errors 2. complete documentation of the header files 3. acknowledgements for the Boost.RangeEx work.

Hi,

Now that the documentation has been updated changing integer_range by iterator_range

template<class Integer> iterator_range< range_detail::integer_iterator<Integer> > irange(Integer first, Integer last);

I will repost my question. I suppose that range_detail can not be used by the user, so how the user can declare the variable returned by irange?

iterator_range< ??? > lower_case = irange(0,10);

Should I use Boost.Typeof?

What about defining a interger_range template class such that 'interger_range <T>' is equivalent of 'iterator_range< range_detail::integer_iterator<T> >', so the user can declare it as

integer_range< int > lower_case = irange(0,10);

Or even better why not upgrade integer_iterator to the public interface?

Is me again, The same hapens with the join function template<typename SinglePassRange1, typename SinglePassRange2> iterator_range<range_detail::join_iterator< typename range_iterator<const SinglePassRange1>::type, typename range_iterator<const SinglePassRange2>::type, typename add_const< typename range_value<const SinglePassRange1>::type>::type>

join(const SinglePassRange1& rng1, const SinglePassRange2& rng2); Shouldn't these two iterators integer_iterator and join iterator be moved to the Boost.Iterator library? Vicente

I will repost my question. I suppose that range_detail can not be used by the user, so how the user can declare the variable returned by irange?

iterator_range< ??? > lower_case = irange(0,10);

Should I use Boost.Typeof?

Ah I see that your question was implied by the < ??? >. There were many questions and it was not obvious that this wasn't just a place holder. I do see your point now. I've been using irange using type deduction, but this would definitely be better if the return type were public. I was trying to avoid adding iterator public types to the range library.

What about defining a interger_range template class such that 'interger_range <T>' is equivalent of 'iterator_range< range_detail::integer_iterator<T> >', so the user can declare it as

integer_range< int > lower_case = irange(0,10);

Yes, this looks like the best solution. I shall make this change as soon as I possibly can get to a computer.

Best, Vicente

Thanks for your persistence. This will definitely improve the library. Regards, Neil Groves