|
Boost : |
From: David Abrahams (dave_at_[hidden])
Date: 2004-05-07 06:02:36
John Torjo <john.lists_at_[hidden]> writes:
> IMO Range library is a too general name, since this is actually just a
> tool to find the metadata (traits) about a range. (In other words, how
> will Matt and me call our library? ;) )
Maybe it's an "iterator range" library?
> And we can think of end(),begin(),... functions as some helpers
> built on top of the library.
>
> Still, I'm ok with it if this will be the general oppinion.
>
> Also, another suggestion:
>
> How about a range_traits class:
>
> template<class C> struct range_traits {
> typedef typename iterator_of<C>::type iterator;
> typedef typename const_iterator_of<C>::type iterator;
> ...etc
> };
>
> It seems to me it provides a more unified of finding metadata about
> a range (and it's a traits class ;)) Has this been suggested
> already?
Degenerate traits "blobs" are a bad idea; they don't interoperate
well with MPL for example.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk