comment on

If your XML is machine-generated and consistent, a line-by-line regular expression might still get you the results faster. But if your preconditions stretch across multiple lines, I'd stay with XML::LibXML.

From my cursory reading of your XML and your source code, it seems that you are interested in the IntDir and OutDir nodes, as "only these can contain the ReleaseDLL directory" (famous last words here). I'd then make the XPath expression more explicit:

# For the IntDir nodes
//PropertyGroup[contains(\@Condition,'$proj')]/IntDir

# For the OutDir nodes
//PropertyGroup[contains(\@Condition,'$proj')]/OutDir
[download]

If you are hell-bent on producing and using one single XPath expression, you can combine the two using the self:: axis. I prefer to avoid such stuff and just keep a list of XPath expressions to run instead:

//PropertyGroup[contains(\@Condition,'$proj')]/*[self::IntDir or self:
+:OutDir]
[download]

In reply to Re: Some questions from beginning user of XML::LibXML and XPath by Corion
in thread Some questions from beginning user of XML::LibXML and XPath by eyepopslikeamosquito

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.


XP is just a number
	PerlMonks