Re: [boost] boost range doc error?

From: Thorsten Ottosen (thorsten.ottosen_at_[hidden])
Date: 2007-10-19 07:54:10

Neal Becker skrev:
> The (recent svn) docs for range talk about boost_range_{begin,end,size}.
> Should't that be just range_{begin,end,size}?

I guess it should. I plan to use some time on my boost libs next week, 
so be patient, please.

As for this issue, then I think we should not change the ADL function 
name to range_begin() etc, simply because the old name has been used for 
so long now for various reason. Thus I plan to change the main trunk 
back to 1.34's names.

As for the docs, then people from the documentation projects have most 
kindly translated the range docs into quickboc, and I will add those 
soon (I tried a while back to install quickbook and all its 
dependencies, but gave up after anights work).

cheers

-Thorsten

> Method 2: provide free-standing functions and specialize metafunctions
>  This procedure assumes that you cannot (or do not wish to) change the types
> that should be made conformant to a Range concept. If this is not true, see
> method 1. 
>  The primary templates in this library are implemented such that certain
> functions are found via argument-dependent-lookup (ADL). Below is given an
> overview of which free-standing functions a class must specify to be
> useable as a certain Range concept. Let x be a variable (const or mutable)
> of the class in question. 
>  Function
>  Related concept
> boost_range_begin(x)  Single Pass Range
>   boost_range_end(x)   Single Pass Range
>   boost_range_size(x)  Forward Range
>   boost_range_begin() and boost_range_end() must be overloaded for both
> const and mutable reference arguments. 
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>