\end{datadesc}
\subsection{Example}
+\nodename{CGI Example}
This example assumes that you have a WWW server up and running,
e.g.\ NCSA's \code{httpd}.
\code{foreground()} and to the FORMS routine \code{fl_init()}.
\subsection{Functions Defined in Module \sectcode{fl}}
+\nodename{FL Functions}
Module \code{fl} defines the following functions. For more information
about what they do, see the description of the equivalent C function
\end{verbatim}\ecode
\section{Standard Modules \sectcode{GL} and \sectcode{DEVICE}}
+\nodename{GL and DEVICE}
\stmodindex{GL}
\stmodindex{DEVICE}
\end{funcdesc}
\subsection{Example}
+\nodename{HTTP Example}
Here is an example session:
\section{Introduction to the profiler}
+\nodename{Profiler Introduction}
A \dfn{profiler} is a program that describes the run time performance
of a program, providing a variety of statistics. This documentation
\section{How Is This Profiler Different From The Old Profiler?}
+\nodename{Profiler Changes}
The big changes from old profiling module are that you get more
information, and you pay less CPU time. It's not a trade-off, it's a
\section{What Is Deterministic Profiling?}
+\nodename{Deterministic Profiling}
\dfn{Deterministic profiling} is meant to reflect the fact that all
\dfn{function call}, \dfn{function return}, and \dfn{exception} events
at this point, when a constant can be used.
-\section{Extensions - Deriving Better Profilers}
+\section{Extensions --- Deriving Better Profilers}
+\nodename{Profiler Extensions}
The \code{Profile} class of module \code{profile} was written so that
derived classes could be developed to extend the profiler. Rather
of STDWIN for C programmers (aforementioned CWI report).
\subsection{Functions Defined in Module \sectcode{stdwin}}
+\nodename{STDWIN Functions}
The following functions are defined in the \code{stdwin} module:
\end{funcdesc}
\subsection{Example}
-\nodename{Stdwin Example}
+\nodename{STDWIN Example}
Here is a minimal example of using STDWIN in Python.
It creates a window and draws the string ``Hello world'' in the top
% XXXJH exceptions: overflow (when? what operations?) zerodivision
\subsubsection{Bit-string Operations on Integer Types}
+\nodename{Bit-string Operations}
Plain and long integer types support additional operations that make
sense only for bit-strings. Negative numbers are treated as their 2's
Modules are written like this: \code{<module 'sys'>}.
\subsubsection{Classes and Class Instances}
+\nodename{Classes and Instances}
% XXXJH cross ref here
(See the Python Reference Manual for these.)
\chapter{THE INTERNET AND THE WORLD-WIDE WEB}
+\nodename{Internet and WWW}
\index{WWW}
\index{Internet}
\index{World-Wide Web}
\end{datadesc}
\subsection{Example}
+\nodename{CGI Example}
This example assumes that you have a WWW server up and running,
e.g.\ NCSA's \code{httpd}.
\code{foreground()} and to the FORMS routine \code{fl_init()}.
\subsection{Functions Defined in Module \sectcode{fl}}
+\nodename{FL Functions}
Module \code{fl} defines the following functions. For more information
about what they do, see the description of the equivalent C function
\end{verbatim}\ecode
\section{Standard Modules \sectcode{GL} and \sectcode{DEVICE}}
+\nodename{GL and DEVICE}
\stmodindex{GL}
\stmodindex{DEVICE}
\end{funcdesc}
\subsection{Example}
+\nodename{HTTP Example}
Here is an example session:
\section{Introduction to the profiler}
+\nodename{Profiler Introduction}
A \dfn{profiler} is a program that describes the run time performance
of a program, providing a variety of statistics. This documentation
\section{How Is This Profiler Different From The Old Profiler?}
+\nodename{Profiler Changes}
The big changes from old profiling module are that you get more
information, and you pay less CPU time. It's not a trade-off, it's a
\section{What Is Deterministic Profiling?}
+\nodename{Deterministic Profiling}
\dfn{Deterministic profiling} is meant to reflect the fact that all
\dfn{function call}, \dfn{function return}, and \dfn{exception} events
at this point, when a constant can be used.
-\section{Extensions - Deriving Better Profilers}
+\section{Extensions --- Deriving Better Profilers}
+\nodename{Profiler Extensions}
The \code{Profile} class of module \code{profile} was written so that
derived classes could be developed to extend the profiler. Rather
of STDWIN for C programmers (aforementioned CWI report).
\subsection{Functions Defined in Module \sectcode{stdwin}}
+\nodename{STDWIN Functions}
The following functions are defined in the \code{stdwin} module:
\end{funcdesc}
\subsection{Example}
-\nodename{Stdwin Example}
+\nodename{STDWIN Example}
Here is a minimal example of using STDWIN in Python.
It creates a window and draws the string ``Hello world'' in the top
% XXXJH exceptions: overflow (when? what operations?) zerodivision
\subsubsection{Bit-string Operations on Integer Types}
+\nodename{Bit-string Operations}
Plain and long integer types support additional operations that make
sense only for bit-strings. Negative numbers are treated as their 2's
Modules are written like this: \code{<module 'sys'>}.
\subsubsection{Classes and Class Instances}
+\nodename{Classes and Instances}
% XXXJH cross ref here
(See the Python Reference Manual for these.)
\chapter{THE INTERNET AND THE WORLD-WIDE WEB}
+\nodename{Internet and WWW}
\index{WWW}
\index{Internet}
\index{World-Wide Web}