[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: AttributeList in C++ SAX

• From: Steinar Bang <sb@m...>
• To: xml-dev@i...
• Date: 12 Oct 1999 13:15:07 +0200

>>>>> Steinar Bang <sb@m...>:

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

And this still is valid for my use of the attributes.

However, my reasons for "going SAX" was to be able at one point, to
throw away my own SAX implementation, or use a different parser
altogether (e.g. to one supporting namespace expansion, and/or one
doing validation).

And at last count 2 out of 4 existing C++ SAX implementations were
returning "const string&".  One of the two even had customers using
the SAX API, so returning "const string&" is what I'll do as well.

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

• References:
  • AttributeList in C++ SAX
    • From: Steinar Bang <sb@m...>
  • Re: AttributeList in C++ SAX
    • From: "Richard Anderson" <rja@a...>
  • Re: AttributeList in C++ SAX
    • From: Steinar Bang <sb@m...>

• Prev by Date: Higher level parsing (Was: Dissillusioned...)
• Next by Date: RE: Dissillusioned about interoperability.
• Previous by thread: Re: AttributeList in C++ SAX
• Next by thread: WAP Binary XML
• Index(es):
  • Date
  • Thread