Date: 2000-01-04 16:09:37
> 3) Constructor that takes a pair of iterators. In the case of carray,
A variation on this that might make sense would be to have a
constructor that takes a single iterator and which always reads in
the number of elements in the carray.
This does not give interoperability with the other containers, but do
we really want that? It seems to me that the inherent semantics of
an iterator-pair constructor is that it should be able to handle
*any* range, not just a fixed range. With this line of reasoning
it does not make sense to define one for this array class.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk