I usually find the CPAN documentation adequate though you do have to read several modules:
XML::LibXML::Element,
XML::LibXML::Node etc. A separate issue is that your documentation problem may be with XPath and not XML::LibXML. I find
http://www.w3schools.com/Xpath/ quite helpful in this regard. The real gotcha however is very often that when you try to parse a wild piece of XML, it often has a namespace set.
The following example I have just grabbed out of some code of mine.
my $parser = XML::LibXML->new();
my $doc = $parser->parse_string($xml_sitemap);
print $doc->getDocumentElement->getNamespaces->getValue, "\n";
my $xpc = XML::LibXML::XPathContext->new();
$xpc->registerNs('x', $doc->getDocumentElement->getNamespaces->getValu
+e);
foreach my $u ($xpc->findnodes('//x:loc/child::text()',$doc)) {
my $url = $u->toString;
.......
}
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.