Know-How für Ihr Projekt

Perl Documentation


XML::LibXML - Perl Binding for libxml2


use XML::LibXML;
my $dom = XML::LibXML->load_xml(string => <<'EOT');
$libxmlnode = XML::LibXML->import_GDOME( $node, $deep );
$gdomenode = XML::LibXML->export_GDOME( $node, $deep );


This module is an interface to libxml2, providing XML and HTML parsers with DOM, SAX and XMLReader interfaces, a large subset of DOM Layer 3 interface and a XML::XPath-like interface to XPath API of libxml2. The module is split into several packages which are not described in this section; unless stated otherwise, you only need to use XML::LibXML; in your programs.

For further information, please check the following documentation:

The nodes in the Document Object Model (DOM) are represented by the following classes (most of which "inherit" from XML::LibXML::Node):


Recall that since version 5.6.1, Perl distinguishes between character strings (internally encoded in UTF-8) and so called binary data and, accordingly, applies either character or byte semantics to them. A scalar representing a character string is distinguished from a byte string by special flag (UTF8). Please refer to perlunicode for details.

XML::LibXML's API is designed to deal with many encodings of XML documents completely transparently, so that the application using XML::LibXML can be completely ignorant about the encoding of the XML documents it works with. On the other hand, functions like XML::LibXML::Document->setEncoding give the user control over the document encoding.

To ensure the aforementioned transparency and uniformity, most functions of XML::LibXML that work with in-memory trees accept and return data as character strings (i.e. UTF-8 encoded with the UTF8 flag on) regardless of the original document encoding; however, the functions related to I/O operations (i.e. parsing and saving) operate with binary data (in the original document encoding) obeying the encoding declaration of the XML documents.

Below we summarize basic rules and principles regarding encoding:

  1. Do NOT apply any encoding-related PerlIO layers (:utf8 or :encoding(...)) to file handles that are an input for the parses or an output for a serializer of (full) XML documents. This is because the conversion of the data to/from the internal character representation is provided by libxml2 itself which must be able to enforce the encoding specified by the <?xml version="1.0" encoding="..."?> declaration. Here is an example to follow:

    use XML::LibXML;
    # load
    open my $fh, '<', 'file.xml';
    binmode $fh; # drop all PerlIO layers possibly created by a use open pragma
    $doc = XML::LibXML->load_xml(IO => $fh);
    # save
    open my $out, '>', 'out.xml';
    binmode $out; # as above
    # or
    print {$out} $doc->toString();
  2. All functions working with DOM accept and return character strings (UTF-8 encoded with UTF8 flag on). E.g.

    my $doc = XML::LibXML::Document->new('1.0',$some_encoding);
    my $element = $doc->createElement($name);
    $xml_fragment = $element->toString(); # returns a character string
    $xml_document = $doc->toString(); # returns a byte string

    where $some_encoding is the document encoding that will be used when saving the document, and $name and $text contain character strings (UTF-8 encoded with UTF8 flag on). Note that the method toString returns XML as a character string if applied to other node than the Document node and a byte string containing the appropriate

    <?xml version="1.0" encoding="..."?>

    declaration if applied to a XML::LibXML::Document.

  3. DOM methods also accept binary strings in the original encoding of the document to which the node belongs (UTF-8 is assumed if the node is not attached to any document). Exploiting this feature is NOT RECOMMENDED since it is considered bad practice.

    my $doc = XML::LibXML::Document->new('1.0','iso-8859-2');
    my $text = $doc->createTextNode($some_latin2_encoded_byte_string);

NOTE: libxml2 support for many encodings is based on the iconv library. The actual list of supported encodings may vary from platform to platform. To test if your platform works correctly with your language encoding, build a simple document in the particular encoding and try to parse it with XML::LibXML to see if the parser produces any errors. Occasional crashes were reported on rare platforms that ship with a broken version of iconv.


XML::LibXML since 1.67 partially supports Perl threads in Perl >= 5.8.8. XML::LibXML can be used with threads in two ways:

By default, all XML::LibXML classes use CLONE_SKIP class method to prevent Perl from copying XML::LibXML::* objects when a new thread is spawn. In this mode, all XML::LibXML::* objects are thread specific. This is the safest way to work with XML::LibXML in threads.

Alternatively, one may use

use threads;
use XML::LibXML qw(:threads_shared);

to indicate, that all XML::LibXML node and parser objects should be shared between the main thread and any thread spawn from there. For example, in

my $doc = XML::LibXML->load_xml(location => $filename);
my $thr = threads->new(sub{
  # code working with $doc

the variable $doc refers to the exact same XML::LibXML::Document in the spawned thread as in the main thread.

Without using mutex locks, parallel threads may read the same document (i.e. any node that belongs to the document), parse files, and modify different documents.

However, if there is a chance that some of the threads will attempt to modify a document (or even create new nodes based on that document, e.g. with $doc->createElement) that other threads may be reading at the same time, the user is responsible for creating a mutex lock and using it in both in the thread that modifies and the thread that reads:

my $doc = XML::LibXML->load_xml(location => $filename);
my $mutex : shared;
my $thr = threads->new(sub{
   lock $mutex;
   my $el = $doc->createElement('foo');
   # ...
  lock $mutex;
  my $root = $doc->documentElement;
  say $root->name;

Note that libxml2 uses dictionaries to store short strings and these dictionaries are kept on a document node. Without mutex locks, it could happen in the previous example that the thread modifies the dictionary while other threads attempt to read from it, which could easily lead to a crash.


Sometimes it is useful to figure out, for which version XML::LibXML was compiled for. In most cases this is for debugging or to check if a given installation meets all functionality for the package. The functions XML::LibXML::LIBXML_DOTTED_VERSION and XML::LibXML::LIBXML_VERSION provide this version information. Both functions simply pass through the values of the similar named macros of libxml2. Similarly, XML::LibXML::LIBXML_RUNTIME_VERSION returns the version of the (usually dynamically) linked libxml2.


By default the module exports all constants and functions listed in the :all tag, described below.



The modules described in this section are not part of the XML::LibXML package itself. As they support some additional features, they are mentioned here.



Although both modules make use of libxml2's XML capabilities, the DOM implementation of both modules are not compatible. But still it is possible to exchange nodes from one DOM to the other. The concept of this exchange is pretty similar to the function cloneNode(): The particular node is copied on the low-level to the opposite DOM implementation.

Since the DOM implementations cannot coexist within one document, one is forced to copy each node that should be used. Because you are always keeping two nodes this may cause quite an impact on a machines memory usage.

XML::LibXML provides two functions to export or import GDOME nodes: import_GDOME() and export_GDOME(). Both function have two parameters: the node and a flag for recursive import. The flag works as in cloneNode().

The two functions allow to export and import XML::GDOME nodes explicitly, however, XML::LibXML allows also the transparent import of XML::GDOME nodes in functions such as appendChild(), insertAfter() and so on. While native nodes are automatically adopted in most functions XML::GDOME nodes are always cloned in advance. Thus if the original node is modified after the operation, the node in the XML::LibXML document will not have this information.


For bug reports, please use the CPAN request tracker on

For suggestions etc., and other issues related to XML::LibXML you may use the perl XML mailing list (, where most XML-related Perl modules are discussed. In case of problems you should check the archives of that list first. Many problems are already discussed there. You can find the list's archives and subscription options at


Matt Sergeant, Christian Glahn, Petr Pajas




2001-2007, Ltd.

2002-2006, Christian Glahn.

2006-2009, Petr Pajas.