"David Abrahams" <dave@boost-consulting.com> wrote in message news:ull5bnykl.fsf@boost-consulting.com... | | 1. What does it take to get support for standard containers as ranges? | According to what I can see in the documentation, the standard | containers don't satisfy the range concepts. IOW, | | begin(v) | | isn't valid when v is a standard vector. | | From what I can tell from browsing the implementation, the | requirement should be: | | boost::begin(v) doens't it seem strange that a concept requirement is bound to a certain namespace? | and the default behavior of boost::begin needs to be documented. it's documented in another document. I provided linke to in in the CVS version some time ago after you requrested it. | 2. http://www.boost.org/libs/range/doc/style.html mentions | SwappableRange. What is that and where is it defined? The only | things I can imagine it meaning are highly counterintuitive. the document talks about terminology. A swappable range would be a range where the iterators are swappable. | 3. Where did you put the documentation that describes the conformance | of built-in strings, arrays, etc. to the Range concepts? in the "Implementation of range concepts". -Thorsten