What about this? use strict;
use XML::LibXML;
parse();
sub parse {
my $filename = shift;
my $parser = XML::LibXML->new();
my $doc = $parser->parse_string(<<'EOT');
<root>
<node>text1
<child1>data</child1>
<child2>data2</child2>
</node>
<node>text2
<child1>blah</child1>
<child2>data3</child2>
</node>
</root>
EOT
foreach my $node ($doc->findnodes('/root/node/text()[1]')) {
print "string value :".$node->string_value."\n";
print "to literal :".$node->to_literal."\n";
print "node name :".$node->nodeName()."\n";
print "____________________\n";
}
}
Output: string value :text1
to literal :text1
node name :#text
____________________
string value :text2
to literal :text2
node name :#text
____________________
ikegami was close, but he missed adding the proximity position of the first member of the node-set (the [1]).
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|