2003-June 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: [Re: [libxml++] Win32 link error (v0.24.0 + msvc patch)],
Murray Cumming
[libxml++] Compiling with Solaris C++ compiler,
Grossmann Niklas
[libxml++] Win32 link error (v0.24.0 + msvc patch),
Matt Esterly
[libxml++] Re: Would like to help w/ libxml++ project,
Christophe de VIENNE
[libxml++] [ libxmlplusplus-Patches-755172 ] msvc compile and distrib for 0.24,
SourceForge.net
[libxml++] 0.24 not compiling in VS6,
Forrest Osterman
Re: [libxml++] Segfault in dom parser,
Thomas Jarosch
[libxml++] Character encoding, UTF-8 and such,
Morten Hanssen
[libxml++] libxml++ 0.24 release,
Christophe de VIENNE
[libxml++] Error Checking in parsers,
Christophe de VIENNE
[libxml++] Patch need to be applied,
Murray . Cumming
RE: [libxml++] indent again,
Murray . Cumming
[libxml++] [ libxmlplusplus-Patches-751868 ] Including <istream> breaks compilaton,
SourceForge.net
[libxml++] Unknown encoding crashes DOM Parser,
p . klotz
[libxml++] xmlpp::DomParser w/ multiple files,
Daniel Hedlund
[libxml++] libxml++ 0.23.0: Patch to remove gcc warnings,
p . klotz
[libxml++] iso-8859-1 encoded characters,
Thomas Jarosch
[libxml++] windows compile error with latest release,
Forrest Osterman
[libxml++] Memory leak?,
Morten Hanssen
Re: [Re: [libxml++] separate parse_*() functions],
Murray Cumming
RE: [libxml++] separate parse_*() functions,
Murray . Cumming
Mail converted by MHonArc
