/*
Called to parse an element. We make a selector from the element name and
then if we respond to selector it is called from here. Selectors we respond
to have an attribute dictionary
Thanks for the responses. In the past I have always used NSXMLParser to take
control of the structures built during parsing.
However, for the past couple years I have used the DOM approach with NSXMLNode
and its descendants. After some experimentation with very large XML files I
have found
I am using NSXMLDocument to parse XML files. Some of the files are not legal
XML because they contain a sequence of top level elements (legal XML must have
a unique root element).
Currently I handle this issue by programmatically adding a root element to
surround the entire file before
On 10/21/12 12:50 PM, Thomas Wetmore wrote:
I am using NSXMLDocument to parse XML files. Some of the files are not legal
XML because they contain a sequence of top level elements (legal XML must
have a unique root element).
Currently I handle this issue by programmatically adding a root element
Doing it programmatically is trivial so I'll stick with it.
Tom Wetmore, CBW, DeadEnds Software
On Oct 21, 2012, at 6:50 AM, Thomas Wetmore wrote:
I am using NSXMLDocument to parse XML files. Some of the files are not legal
XML because they contain a sequence of top level elements (legal XML
On 21/10/2012, at 9:50 PM, Thomas Wetmore t...@verizon.net wrote:
Is there a way to easily parse an XML file consisting of a sequence of top
level elements?
What about NSXMLParser? This gives you finer-grained access to the XML without
expecting a specific structure (other than valid XML).
