Request for Discussion: SAX 1.0 in C++

[Steinar Bang]

>>>>> roddey at us.ibm.com:

> John is absolutely correct. It *must* be wchar_t if its going to be
> a fixed thing.

Please note that John was advocating std::wstring, rather than
std::wchar_t*.

I'll live with it, if that's what the standard SAX for C++ ends up
with, but unhappily, since this will make for unefficient handling on
gcc. :-/

> 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.

Actually I think it would be much easier on debuggers and editors and
me, if I could store the text constants in UTF-8.

> 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.

Using data on the fly is what I want to do.  That's why I prefer to
get it in the form I will use it.

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