[EMAIL PROTECTED] wrote:
>> Actually, DOMString seems to be somewhere between Java's and basic_string
>> semantics.

>Oops, I really meant StringBuffer, not String.

Yea, it is closer to StringBuffer().  However, the Java bindings are written in terms 
of String's.

>If it's immutable, then operator=() is out of the question.  Do you mean
>conversion from DOMString to some other string type?  Or conversion to
>DOMString from some other string type?

I was talking templates defining operator= overloads that would convert const 
DOMString&'s to basic_strings.

>I would really like to see XMLCh* as the representation for strings.  I
>think that's the simplest thing, and you can always copy that to a
>basic_string<XMLCh> if you want.  Also, there are plenty of manipulation
>functions that will accept XMLCh* for times when you want to do read-only
>operations.

Right now, I'm just trying to get my mind around what Andy has done so far.  It does 
appear that all the interfaces are defined in terms of XMLCh*'s, not a DOMString in 
sight.  I'm not adverse to
defining the interfaces in terms of const XMLCh*'s, I'm just hostile to the current 
DOMString.

I've run some profiles on both the existing threadtest and ithreadtest.  

The first thing that is interesting is that IDParentNode::insertBefore takes about 15% 
of the total time, a lot of that checking for hierarchy and ownership errors shouldn't 
occur when building the
DOM from a file (but do need to be checked when calling the DOM from an application).

About 6% of the time is taken in the UTF8 transcoder (this on a file with no 
characters with code higher than points than 127).  Seems like that could be whittled 
down a bit.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to