> David N Bertoni wrote:
> >This would be great, as long as it can be aligned with what the
standards
> >bodies are doing.
> The W3C/NIST effort seems to be exploring alternatives at this time,
especially regarding multi-language issues. Doing a > CppUnit variant of
the current NIST Java tests would provide something for
> them to look at for C++.
> >And don't forget that for DOM compliance
> >you must be able to represent a value as both "null" _and_ empty, so you
> >cannot just return a reference to an instance of a string class, you
have
> >to return a pointer.
>
> The same issue applies to all the node classes, DOM_Element, DOM_Node,
etc. They
> addressed it by supplying a operator==(void*). I don't think there is
anything special
> about DOMString that would make the approach fine for DOM_Node and
inappropriate for
> DOMString.
Except the current semantics for DOMString are like that of a Java String,
which is always a reference, so representing null is pretty natural. For a
class having more C++-like semantics (value semantics), it would be really
weird to have an operator==(void*) that works like the original
DOMString's. Not to mention that the implementation would be kind of
difficult and strange. Did you have something in mind for this?
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
