Re: [boost] iterator_facade, decoupling of access and traversal?

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-05-24 07:19:24

Roland Schwarz schrieb:

> So I am wondering if I understand something wrong? Isn't the
> decoupling of access and traversal meant to allow "Reference" be
> a proxy object?

On page
http://www.boost.org/doc/libs/1_35_0/libs/iterator/doc/new-iter-concepts.html

I read:

> A difficult design decision concerned the operator[].
...
> operator[] is only required to return something convertible to the
> value_type (for a Readable Iterator), and is required to support
> assignment i[n] = t (for a Writable Iterator).

So I believe my intended interator is categorized as
Readable, Writeable, Random access traversal

However operator[] returns something that is convertible to
"reference" and not to value_type (as I expected). Can this
behaviour of iterator_facade be controlled somehow?

-- 
_________________________________________
  _  _  | Roland Schwarz
 |_)(_  | aka. speedsnail
 | \__) | mailto:roland.schwarz_at_[hidden]
________| http://www.blackspace.at