From: David Abrahams (dave_at_[hidden])
Date: 2003-10-06 20:37:00
Brian McNamara <lorgon_at_[hidden]> writes:
> Maybe another way to state my point is that I see container_traits as a
> "concept wrapper" rather than a "module". It takes a concept (as
> described by, e.g., the standard) and wraps it in a more convenient and
> generic interface. This allows more types to model the concept (e.g.
> an array can be a Container when viewed via container_traits) and
Your language, if not your thinking, is somewhat muddled at this
point. Maybe you need to rephrase for the rest of us? Either an
array satisfies the Container concept or it doesn't. Unless you're
changing the standard Container concept, it doesn't.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk