OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: SAX an working of the Parser

Hi Jan,

"Zmitko, Jan" <Jan.Zmitko@ADBag.de> writes:

> can someone explain me how a parser works internally under the usage of =
> SAX. How can the parser detect, that the document is not well formed or =
> not valid. After each event respectively callback the parser doesn=B4t =
> know more about the element. How it=B4s possible to check that some =
> elements later the document is not closed correctly (for example)? Use a =
> parser temporaly an internal cache for a range of nodes, or the like?

A SAX parser normally uses a stack to keep track of elements that
have been opened but haven't been closed yet.


Boris Kolpackov
Code Synthesis Tools CC
Open-Source, Cross-Platform C++ XML Data Binding

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS