in reply to Re: Mixed XML content with XML::LibXML
in thread Mixed XML content with XML::LibXML

ikegami was close, but he missed adding the proximity position of the first member of the node-set (the [1]).

I most definitely did not want to drop some of the text.

  • Comment on Re^2: Mixed XML content with XML::LibXML

Replies are listed 'Best First'.
Re^3: Mixed XML content with XML::LibXML
by CountZero (Bishop) on Sep 29, 2008 at 19:52 UTC
    For lack of a DTD, you could not know whether there was to be additional text-data, but from the example given it seemed that there was only one such item and the OP confirmed later that this was indeed the case.

    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

      So why use [1] if there's only going to be one?
        There is some whitespace between the <child>-nodes that gets picked-up as significant text it appears. If you run your example with text() in the XPath-expression it shows FIVE results and not the expected FOUR.

        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