• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: XSXMLNode nodesForXPath bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XSXMLNode nodesForXPath bug?


  • Subject: Re: XSXMLNode nodesForXPath bug?
  • From: "Stephen Deken" <email@hidden>
  • Date: Fri, 8 Jun 2007 21:07:32 -0500

On 6/8/07, Stephen Deken <email@hidden> wrote:
That seems like it should work too, but the string() function
apparently doesn't work in that context -- it causes the query to
return nil without setting an error.

Ah, ah -- that sort of construct doesn't work when dealing with straight XPath (nodesForXPath:error:) but works a treat when using XQuery (objectsForXQuery:error:).

The problem with the descendant::text() query remains, but at least
there's a sane workaround.

--
Stephen Deken
email@hidden
_______________________________________________

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


References: 
 >XSXMLNode nodesForXPath bug? (From: "Stephen Deken" <email@hidden>)
 >Re: XSXMLNode nodesForXPath bug? (From: Tomas FranzĂ©n <email@hidden>)
 >Re: XSXMLNode nodesForXPath bug? (From: "Stephen Deken" <email@hidden>)

  • Prev by Date: Re: Key number to Unicode string
  • Next by Date: Re: programmatically adding model objects to NSOultineView/NSTreeController
  • Previous by thread: Re: XSXMLNode nodesForXPath bug?
  • Next by thread: CoreData and image caching
  • Index(es):
    • Date
    • Thread