• 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: NSXMLParserTroubles (errors and line/column positions wrong?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSXMLParserTroubles (errors and line/column positions wrong?)


  • Subject: Re: NSXMLParserTroubles (errors and line/column positions wrong?)
  • From: Andy Satori <email@hidden>
  • Date: Fri, 23 Jan 2004 15:20:05 -0500

Jim,

I ultimately abandoned NSXMLParser altogether because of this and similar issues. I now have a new XML class that I've built on top of libXML. It's a workable solution, but at this point it is very immature. NSXMLParser strikes me as a half implemented feature that wasn't implemented to meet a specific need but more to fulfill a 'Feature Request' without much attention to details, it works fine for valid syntax XML files, but for anything more robust, it just isn't there.

I spent some time on SourceForge a little earlier today evaluating the idea of taking my foundation and making an open source framework for robust XML and XSLT handling, using libXML and libXSLT as a base layer, until such time as they either don't suit the need any more.


Andy



On Jan 23, 2004, at 2:06 PM, Jim Correia wrote:

On Jan 23, 2004, at 1:53 PM, Don Briggs wrote:

On Jan 23, 2004, at 9:33 AM, Jim Correia wrote in part:
Does anyone have experience using NSXMLParser? Are these just bugs? (In which case I'll file a bug report.) Or am I using the class incorrectly?

I have some VERY old code on my .Mac Public folder (.Mac user donbriggs).
Look for XMLChecker.dmg.
It's TextEdit with some hooks to the XML stuff for parsing.
I just recompiled it, and it seems still to highlight the line of an XML error.
Open source.
Enjoy.

Thanks Don. Your sample is using the CFXMLParser which works ok for me. If I build on top of NSXMLParser (different core?) I run into the problems mentioned.

Jim
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: NSXMLParserTroubles (errors and line/column positions wrong?)
      • From: Vince DeMarco <email@hidden>
References: 
 >NSXMLParserTroubles (errors and line/column positions wrong?) (From: Jim Correia <email@hidden>)
 >Re: NSXMLParserTroubles (errors and line/column positions wrong?) (From: Don Briggs <email@hidden>)
 >Re: NSXMLParserTroubles (errors and line/column positions wrong?) (From: Jim Correia <email@hidden>)

  • Prev by Date: Re: CURLHandle example code?
  • Next by Date: Re: XCode annoyance :-\
  • Previous by thread: Re: NSXMLParserTroubles (errors and line/column positions wrong?)
  • Next by thread: Re: NSXMLParserTroubles (errors and line/column positions wrong?)
  • Index(es):
    • Date
    • Thread