Re: [boost] indirect_iterator

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-06-27 10:16:21

For the deduction to work, you have to have *two* non-pointer iterators
with well-defined traits. So, a std::list<T*>::iterator won't work, but a
std::list<std::list<T>::iterator>::iterator should work. Does that clear
anything up?

As for the documentation, please submit a patch.

Thanks,
Dave

----- Original Message -----
From: "Yitzhak Sapir" <yitzhaks_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, June 27, 2002 11:58 AM
Subject: [boost] indirect_iterator

> In trying to use the indirect_iterator on MSVC 6.5 I found that I cannot
rely on indirect_iterator to automatically compute the value_type from the
iterator_traits.  This despite the document saying: "In most cases the type
of the elements being pointed to can be deduced using std::iterator_traits,
but in some situations the user may want to override this type" although
this gives no hint that any use of MSVC is one such "situation."  I don't
think MSVC would have a problem with iterator traits except for true
pointer types.  This is using boost 1.28.  So, my question is why is this
necessary for non-pointer types that have well defined iterator_traits? and
also, I thought I might suggest that it would be nice if the documentation
covered this (for example, "in some situations, the user may want to
override this type... On some compilers, the user may need to specify the
value_type").
> _______________________________________________
> Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost