Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
48971198
Commit
48971198
authored
Dec 13, 2000
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Finish a sentence that was left half-written!
parent
0e76ab2e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
20 additions
and
16 deletions
+20
-16
Doc/lib/xmlsax.tex
Doc/lib/xmlsax.tex
+20
-16
No files found.
Doc/lib/xmlsax.tex
View file @
48971198
...
...
@@ -43,25 +43,29 @@ The convenience functions are:
\end{funcdesc}
A typical SAX application uses three kinds of objects: readers,
handlers and input sources. ``Reader'' in this context is another term
for parser, ie. some piece of code that reads the bytes or characters
from the input source, and produces a sequence of events. The events
then get distributed to the handler objects, ie. the reader invokes a
method on the handler. A SAX application must therefore obtain a
handler object, create or open the input sources, create the handlers,
and connect these objects all together. As the final step, parsing is
invoked. During parsing
handlers and input sources. ``Reader'' in this context is another
term for parser, i.e.
\
some piece of code that reads the bytes or
characters from the input source, and produces a sequence of events.
The events then get distributed to the handler objects, i.e.
\
the
reader invokes a method on the handler. A SAX application must
therefore obtain a reader object, create or open the input sources,
create the handlers, and connect these objects all together. As the
final step of preparation, the reader is called to parse the input.
During parsing, methods on the handler objects are called based on
structural and syntactic events from the input data.
For these objects, only the interfaces are relevant; they are normally
not instantiated by the application itself. Since Python does not have
not instantiated by the application itself.
Since Python does not have
an explicit notion of interface, they are formally introduced as
classes. The
\class
{
InputSource
}
,
\class
{
Locator
}
,
\class
{
AttributesImpl
}
, and
\class
{
XMLReader
}
interfaces are defined
in the module
\refmodule
{
xml.sax.xmlreader
}
. The handler interfaces
are defined in
\refmodule
{
xml.sax.handler
}
. For convenience,
\class
{
InputSource
}
(which is often instantiated directly) and the
handler classes are also available from
\module
{
xml.sax
}
. These
classes are described below.
classes, but applications may use implementations which do not inherit
from the provided classes. The
\class
{
InputSource
}
,
\class
{
Locator
}
,
\class
{
AttributesImpl
}
,
\class
{
AttributesNSImpl
}
, and
\class
{
XMLReader
}
interfaces are defined in the module
\refmodule
{
xml.sax.xmlreader
}
. The handler interfaces are defined in
\refmodule
{
xml.sax.handler
}
. For convenience,
\class
{
InputSource
}
(which is often instantiated directly) and the handler classes are
also available from
\module
{
xml.sax
}
. These interfaces are described
below.
In addition to these classes,
\module
{
xml.sax
}
provides the following
exception classes.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment