2003-September 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.
[libxml++] [ libxmlplusplus-Patches-815073 ] Prevent warnings from gcc -Wcast-qual,
SourceForge.net
[libxml++] write_to_stream speed,
Christophe de Vienne
[libxml++] Document interface,
Christophe de VIENNE
RE: [libxml++] libxml++ future - strings and overloaded helper fu nctions,
Murray . Cumming
[libxml++] libxml++ future,
Christophe de Vienne
[libxml++] [ libxmlplusplus-Patches-812758 ] wrap xmlOutputBuffer to implement Document.write_to_stream,
SourceForge.net
[libxml++] libxml++ 0.26 release,
Christophe de Vienne
[libxml++] [ libxmlplusplus-Patches-810606 ] Element::add_comment(),
SourceForge.net
[libxml++] Removing Node::add_attribute(),
Murray . Cumming
[libxml++] Release soon,
Christophe de Vienne
[libxml++] [ libxmlplusplus-Patches-806083 ] call xmlInitParser() to avoid threading problems,
SourceForge.net
Re: [[libxml++] [PATCH] clear_internal_subset()],
Murray Cumming
Re: [Re: [libxml++] namespace support],
Murray Cumming
Re: [[libxml++] Thread safety?],
Murray Cumming
[libxml++] Thread safety?,
Fredrik Arnerup
[libxml++] [PATCH] clear_internal_subset(),
Thomas Jarosch
[libxml++] namespace support,
Murray Cumming
[libxml++] libxml++ problem,
tim
Mail converted by MHonArc
