eprecated or scheduled-for-deprecation
methods. This presents no real problem, however; it just makes you dig
into Apple's documentation more carefully (which I personally found to
be a helpful learning "feature" in itself). It is an excellen
you a mention unless you
object.
-- Josh Caswell
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/
> 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
>This error is the parser state, which since you explicitly aborted ?>the
>parse, will be something like >"NSXMLParserDelegateAbortedParseError" -512.
Yes, as I said in my original post. The parser's delegate gets error
512, NSXMLParserDelegateAbortedParseError, in the delegate method
-parser:par
.") is used for an alert
sheet as I described.
I'm just wondering why, after my delegate aborts the parse, the parser
changes the error code.
-- Josh Caswell
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
This is a copy-paste of a question I asked on StackOverflow <
http://stackoverflow.com/questions/5132266/nsxmlparser-error-code-changes-after-abort>,
which hasn't gotten any answers. I'm still curious about it and hoped I
might get a response on this list; apologies to anyone who is reading it
twic
