AttributeList in C++ SAX

Steinar Bang sb at
Wed Oct 6 14:57:17 BST 1999

>>>>> "Richard Anderson" <rja at>:

> This is cross platform / multiple encoding so we do use wstring.
> We've got some simply conversion shim for help people go between
> wide and narrow I'll post if they would be useful.

I'm not sure what this is, so sure go ahead...! :-)

I'm currently operating with string, and decoding UTF-8 into
ISO8859-1, and throwing away everything that doesn't fit.  This works
for now, because Latin 1 in UTF-8 is all we ever dump.

We'll move to wstring throughout our system later on.

>> In both cases we'll end up assigning to a local variable and do some
>> testing:

> And both cases end up with longer code. 

YMMV here I think.  When I replaced my const string&-returning
AttributeList, with one where the caller has to supply the string to
copy into, I came out the same (except this one works...:-) )

But then I iterate through all attributes of an element and fill the
result into variables, that have a default and are sent to a

I don't ask for attributes by name.

> I prefer the approach we've taken although you cant tell the
> difference between not present and empty string.

> The same feedback has come from our customers who were involved last year
> when putting together the original include files together.

> I guess at the end of the day you have to find a comprimise between
> usability and pureness.

The good thing about my string as argument alternative is the
possibility for minimizing string copies.  I can UTF-8 decode directly
into the string I use all the way into callback class arguments
(ie. one copy may be enough).

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