2003-November Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
Re: [libxml++] sax parser,
Christophe de Vienne
RE: [libxml++] SAX2 (was xmlCreatePushParserCtxt() docs wrong (wa s RE: [libxml+ + ] sax_pars er example: entity not defined)),
Murray . Cumming
[libxml++] SAX2 (was xmlCreatePushParserCtxt() docs wrong (wa s RE: [libxml+ + ] sax_pars er example: entity not defined)),
Murray . Cumming
RE: [libxml++] RE: [xml] xmlCreatePushParserCtxt() docs wrong (wa s RE: [libxml++ ] sax_pars er example: entity not defined),
Murray . Cumming
[libxml++] RE: [xml] xmlCreatePushParserCtxt() docs wrong (was RE: [libxml++ ] sax_pars er example: entity not defined),
Murray . Cumming
xmlCreatePushParserCtxt() docs wrong (was RE: [libxml++] sax_pars er example: entity not defined),
Murray . Cumming
[libxml++] [ libxmlplusplus-Patches-846883 ] derived DOM example,
SourceForge.net
[libxml++] sax_parser example: entity not defined,
Murray Cumming
[libxml++] Dependencies...,
Paul Breslin
[libxml++] [ libxmlplusplus-Patches-842730 ] TextReader,
SourceForge.net
[libxml++] DomParser Thread segmentation fault,
gro_com
[libxml++] ANNOUNCE: libxml++ 0.27,
Christophe de VIENNE
Re: [libxml++] Rename Element::add_content() to add_text_content?,
Murray Cumming
Mail converted by MHonArc
