Incompatible changes: Version 2 of libxml2 is the first version introducing serious backward
-incompatible changes. The main goals were:
- - a general cleanup. A number of mistakes inherited from the very early
+incompatible changes. The main goals were:
- a general cleanup. A number of mistakes inherited from the very early
versions couldn't be changed due to compatibility constraints. Example
the "childs" element in the nodes.
- Uniformization of the various nodes, at least for their header and link
@@ -25,8 +24,7 @@ incompatible changes. The main goals were:
changed to compile against version 2.x of libxml. Here is a list of changes
that I have collected, they may not be sufficient, so in case you find other
change which are required, drop me a
-mail:
- - The package name have changed from libxml to libxml2, the library name
+mail:
- The package name have changed from libxml to libxml2, the library name
is now -lxml2 . There is a new xml2-config script which should be used to
select the right parameters libxml2
- Node childs field has been renamed
@@ -46,8 +44,7 @@ mail:
and formatting the document content becomes significant. So they are
reported by SAX and if your using the DOM tree, corresponding nodes are
generated. Too approach can be taken:
-
- - lazy one, use the compatibility call
+
- lazy one, use the compatibility call
xmlKeepBlanksDefault(0) but be aware that you are
relying on a special (and possibly broken) set of heuristics of
libxml to detect ignorable blanks. Don't complain if it breaks or
@@ -57,8 +54,7 @@ mail:
nodes. You can spot them using the commodity function
xmlIsBlankNode(node) returning 1 for such blank
nodes.
-
- Note also that with the new default the output functions don't add any
+ Note also that with the new default the output functions don't add any
extra indentation when saving a tree in order to be able to round trip
(read and save) without inflating the document with extra formatting
chars.
@@ -74,8 +70,7 @@ mail:
byte of the head of the document available for character detection.
Ensuring both libxml-1.x and libxml-2.x compatibilityTwo new version of libxml (1.8.11) and libxml2 (2.3.4) have been released
to allow smooth upgrade of existing libxml v1code while retaining
-compatibility. They offers the following:
- - similar include naming, one should use
+compatibility. They offers the following:
- similar include naming, one should use
#include<libxml/...> in both cases.
- similar identifiers defined via macros for the child and root fields:
respectively xmlChildrenNode and
@@ -83,8 +78,7 @@ compatibility. They offers the following:
- a new macro LIBXML_TEST_VERSION which should be
inserted once in the client code
So the roadmap to upgrade your existing libxml applications is the
-following:
- - install the libxml-1.8.8 (and libxml-devel-1.8.8) packages
+following:- install the libxml-1.8.8 (and libxml-devel-1.8.8) packages
- find all occurrences where the xmlDoc root field is
used and change it to xmlRootNode
- similarly find all occurrences where the xmlNode
|
