+1
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Andy Heninger/Cupertino/[EMAIL PROTECTED] on 01/12/2000 03:58:21 PM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: xalan-c Problem with Xerces initialization
Joe Gregorio writes,
> The simple answer is to take transcode() out of DOMString.
> [Take out print() and println() while you're at it.] A string
> class should just be a container for char or wchar_t. Transcoding
> and printing are functions to be applied to containers.
> You might want to consider moving
> to wstring in place of DOMString. (You knew that was coming ;-))
>
I'm in favor of taking print() and println() out of DOMString. They were
there for ease of debugging in the early days, but there's not much excuse
for them now.
I don't know how much squawk we would get from doing this, though. I'd
like
to hear any opinions on the question.
transcode() has to stay, however. It's the one relatively straight forward
way to get the string data back to char *, and building the equivalent of
print() using transcode is trivial.
-- Andy
