Howdy,
The existing C++ bindings for libxml, the libxmlplusplus library, seem to
support, basically, just parsing an existing XML document.
I've been working on C++11 bindings that provide a more complete, thread-safe
tree, parser, entities, xmlsave, and xpath API coverage:
http://www.lib
Nikita Churaev writes:
I'm glad that the layer of abstraction helped you personally, but
libxml2 really needs to be usable as-is and the GObject wrappers (GXml,
etc.) should just be trivial things. If wrappers are made but the
libxml2 itself is kept in this current insane state, it'll just becom
Daniel Veillard writes:
Interesting. Though it seems that it's not very common to have
reader/writer accesses by applications on a document. Usually it's
either data gathering, and exclusively document read/xpath etc... or
their serializer counter part and then the whole document is saved
as w
Nikolay Sivov writes:
On 4/10/2014 16:20, Bart De Schuymer wrote:
Hello,
We tried using libxml2 configured with the --with-fexceptions option and
have identified a memory leak when our C++ startElement callback throws an
exception.
The cause of the leak is as follows:
xmlParseStartTag fr
