I think it is valuable to remain abstract in DOMString
since we may want to allow specific optimizations that
are not appropriate in a generic basic_string<XMLCh*>.
However, it might be possible to morph DOMString so
that it has identical semantics to a subset of
basic_string and could either be implemented as
class DOMString : private std::basic_string<XMLCh*>
{
public:
//
// override the private access of supported methods
};
-- or --
class DOMString
{
//
// a DOM specific implementation of a subset
};
This would allow both use of basic_string or DOMString
at the builders choice.
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
