Date: 2000-01-12 20:15:47
Here's another stab at the reference type requirement. I think this
provides the flexibility that Dave wants, while also protected the
cases I'm interested in.
The reference type does not have to be a real C++ reference. The
requirements of the reference type depend on the context within which
the Collection is being used. Specifically it depends on the
requirements the context places on the value type of the Collection.
The reference type of the Collection must meet the same requirements
as the value type. Note that it is permissable for the reference type
to be a Proxy class, but only in contexts where there are not
requirements for member access on the value type, since it is
impossible for a proxy class to provide member access due to the lack
of an overloadable member access operator. Also note it is
permissable for the reference type to be the value type itself. It
would not be appropriate to use the reference type for a function
argument with the intent that the argument will be pass-by-reference.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk