Edited Contributors
infrastructure for xpath
interface: first commit
example for xpath
integration in document and node
first version working
implementing node_set::contains
a few inconsistencies
iterator copy fixed
a few tests
reimplementing node_set::contains
renamed registerNamespace to register_namespace
removed operator-- (wasn't neccessary)
correct handling of incorecct xpath-queries
Merge branch 'thriqon-xpath-rebased' into xpath
Use errors.h, not the old exception.h.
Add xpath files to Windows build.
Use xmlXPathEval instead of xmlXPathEvalExpression.

It's the preferred one, see
https://mail.gnome.org/archives/xml/2005-August/msg00156.html:

    > what is the difference between the functions xmlXPathEval and
    > xmlXPathEvalExpression, that are defined in "xpath.c"? Which one should
    > I use? I've looked at the source code, but I'm not so familiar with
    > libxml2 internals to understand details.

    Difference is historical, I would say use xmlXPathEval().

    Daniel
Use nodes_view for XPath.

Instead of another node_set class.

In the process, remove broken tests (e.g.  advancing end()) and do misc
tests cleanup, e.g.  add test_file_path() uses.
Allows invalid nodes_view iterators.

Make it possible to explicitly specify NULL function and data without
asserting.  This is useful for conveniently creating empty views with
the default ctor (which was broken before).