• 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
Fwd: NSXMLParserDelegateAbortedParseError
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: NSXMLParserDelegateAbortedParseError


  • Subject: Fwd: NSXMLParserDelegateAbortedParseError
  • From: Josh Caswell <email@hidden>
  • Date: Tue, 08 Mar 2011 13:51:17 -0800

> So you are not getting a parsing error, you're using the wrong mechanism.

I think I see what you are saying. When my parser encounters an
element called "Error", I know that I don't need any more parsing done
no matter what else is in the data, so it seemed sensible to have the
delegate stop the parser right then. But in fact, -abortParse is
intended to be used for other circumstances?
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please 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: 
 >NSXMLParserDelegateAbortedParseError (From: Kevin Bracey <email@hidden>)
 >Re: NSXMLParserDelegateAbortedParseError (From: Josh Caswell <email@hidden>)
 >Re: NSXMLParserDelegateAbortedParseError (From: Kevin Bracey <email@hidden>)

  • Prev by Date: Re: How to wait for methods with result/completion blocks to finish?
  • Next by Date: Core Data Intermittently Blocked Over AFP?
  • Previous by thread: Re: NSXMLParserDelegateAbortedParseError
  • Next by thread: Fwd: NSXMLParserDelegateAbortedParseError
  • Index(es):
    • Date
    • Thread