It was the removal of the two methods. The string semantics should still be
discussed but its a longer term issue. The immediate issue at hand was
getting rid of the extraneous printing methods before we solidify for the
next release.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
"Arnold, Curt" <[EMAIL PROTECTED]> on 01/12/2000 04:22:30 PM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: xalan-c Problem with Xerces initialization
It was ambiguous what Dean was +1'ing. I assume it was the removal of
println() and print() and not a move to wstring.
I had previously mentioned making DOMString's semantics match that of a
subset of wstring, so that a user could have a familiar behavior and it
would be possible (though not tested and supported) that you could redefine
DOMString to be derived from wstring. I haven't had any free time
recently,
but I could take a shot at scoping the effect. Is it worth trying?
