Re: XSXMLNode nodesForXPath bug?
Re: XSXMLNode nodesForXPath bug?
- Subject: Re: XSXMLNode nodesForXPath bug?
- From: Tomas Franzén <email@hidden>
- Date: Fri, 8 Jun 2007 23:20:27 +0200
On 8 jun 2007, at 22.04, Stephen Deken wrote:
But this returns all manner of crap that's unrelated to what I want
and completely outside the anchors I'm interested in. If I add a
technically useless constraint:
//a[starts-with(@href,'forumdisplay')]
/descendant::text[ancestor::a[starts-with(@href,'forumdisplay')]]
...then I get back what I'm looking for, even though the ancestor
constraint should be completely useless. Should I really have to note
that I only want the descendants who have me as an ancestor?
Hi Stephen,
That's odd. I can't think of why it does this. Depending on exactly
what you need to accomplish, perhaps you could use something like this:
//a[starts-with(@href,'forumdisplay')]/string()
Still, the problem you pointed out is indeed strange.
Tomas Franzén
Lighthead Software
http://www.lightheadsw.com/
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden