|
Boost Users : |
From: Duane Murphy (duanemurphy_at_[hidden])
Date: 2002-01-12 14:20:09
There is a comment in iterator_adaptors:
public: // implementation details (too many compilers have trouble when
these are private).
Policies& policies() { return m_iter_p.second(); }
const Policies& policies() const { return m_iter_p.second(); }
Base& iter() { return m_iter_p.first(); }
const Base& iter() const { return m_iter_p.first(); }
This seems to imply that iter() and policies() ought to be private. I
would like to suggest that having access to the underlying iterator is
valuable. This is especially true of transform and projection iterators
which allow you to locate a record by searching on a field. Access to the
underlying iterator gets access to the rest of the record.
Is there some other way of accomplishing the same thing without using iter()?
Thanks,
...Duane
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net