Request for Discussion: SAX 1.0 in C++

roddey at roddey at
Mon Dec 20 19:17:18 GMT 1999

>It seems to me that code like:
>void DocumentHandler::startElement (
>    const std::wstring &name, const AttributeList &atts)
>    if (name == L"Paragraph") ...
>is going to be a whole lot neater than
>void DocumentHandler::startElement (
>    const std::basic_string<SAXChar> &name, const AttributeList &atts)
>    static const SAXChar paraString[] =
>        {'P','a','r','a','g','r','a','p','h',\0'};
>    if (name == paraString) ...

John is absolutely correct. It *must* be wchar_t if its going to be a fixed
thing. The massive convenience this provides to people who actually want to
do something with the data and for the ability to use constants (look at
XML4C if you want to see what a pain in the butt it is to do the latter
scheme) is paramount. For those folks who need to store text, they can
certainly strip off unwanted bytes before storing it. It is much more
reasonable to require transcoding of people storing text than to require
everyone using the data on the fly to transcode.

Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list