2003-April 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++] xmlpp::Document::write_to_file non const], Murray Cumming
  • [libxml++] xmlpp::Document::write_to_file non const, andy . glew
  • [libxml++] memory leak in SaxParser, thierry
  • [libxml++] [ libxmlplusplus-Patches-724953 ] new node types support, SourceForge.net
  • Re: [Unhandled node types (was: Re: [libxml++] [ libxmlplusplus-Patches-719921 ] patch to make it co, Murray Cumming
  • RE: [libxml++] [ libxmlplusplus-Patches-719921 ] patch to make it compile on NetBSD, Murray . Cumming
  • [libxml++] [ libxmlplusplus-Patches-719921 ] patch to make it compile on NetBSD, SourceForge.net
  • [libxml++] Re: [xml] libxml2 review in windows::developer, Stefan Seefeld
  • [libxml++] [ libxmlplusplus-Patches-718753 ] fix for spec file, SourceForge.net
  • [libxml++] Releasing an RPM?, Cyril Bortolato
  • [libxml++] win32, Paul Maguire
  • [libxml++] Libxml++ on Solaris: the final word., Andrea Vallinotto
  • [libxml++] Return value of SaxParser::on_get_entity(), Jonathan Wakely

  • Mail converted by MHonArc