added nodename macro calls for new very long section names
This commit is contained in:
parent
e56db434a9
commit
86cb0928e3
|
@ -136,6 +136,7 @@ the CGI documentation for a description of the various fields.
|
|||
\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}.
|
||||
|
|
|
@ -34,6 +34,7 @@ FORMS with pure GL windows.
|
|||
\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
|
||||
|
|
|
@ -185,6 +185,7 @@ main()
|
|||
\end{verbatim}\ecode
|
||||
|
||||
\section{Standard Modules \sectcode{GL} and \sectcode{DEVICE}}
|
||||
\nodename{GL and DEVICE}
|
||||
\stmodindex{GL}
|
||||
\stmodindex{DEVICE}
|
||||
|
||||
|
|
|
@ -103,6 +103,7 @@ methods.
|
|||
\end{funcdesc}
|
||||
|
||||
\subsection{Example}
|
||||
\nodename{HTTP Example}
|
||||
|
||||
Here is an example session:
|
||||
|
||||
|
|
|
@ -43,6 +43,7 @@ I'd appreciate the feedback.
|
|||
|
||||
|
||||
\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
|
||||
|
@ -54,6 +55,7 @@ examine the results of a profile operation.
|
|||
|
||||
|
||||
\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
|
||||
|
@ -209,6 +211,7 @@ manual, or guess what the following functions do:
|
|||
|
||||
|
||||
\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
|
||||
|
@ -604,7 +607,8 @@ performance section, and there is no reason to use a variable lookup
|
|||
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
|
||||
|
|
|
@ -21,6 +21,7 @@ For a complete description of STDWIN please refer to the documentation
|
|||
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:
|
||||
|
||||
|
@ -735,7 +736,7 @@ Discard the text-edit object. It should not be used again.
|
|||
\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
|
||||
|
|
|
@ -206,6 +206,7 @@ See the section on built-in functions for an exact definition.
|
|||
% 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
|
||||
|
@ -483,6 +484,7 @@ defines \code{\var{m}.a} to be \code{1}, but you can't write \code{\var{m}.__dic
|
|||
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.)
|
||||
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
\chapter{THE INTERNET AND THE WORLD-WIDE WEB}
|
||||
\nodename{Internet and WWW}
|
||||
\index{WWW}
|
||||
\index{Internet}
|
||||
\index{World-Wide Web}
|
||||
|
|
|
@ -136,6 +136,7 @@ the CGI documentation for a description of the various fields.
|
|||
\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}.
|
||||
|
|
|
@ -34,6 +34,7 @@ FORMS with pure GL windows.
|
|||
\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
|
||||
|
|
|
@ -185,6 +185,7 @@ main()
|
|||
\end{verbatim}\ecode
|
||||
|
||||
\section{Standard Modules \sectcode{GL} and \sectcode{DEVICE}}
|
||||
\nodename{GL and DEVICE}
|
||||
\stmodindex{GL}
|
||||
\stmodindex{DEVICE}
|
||||
|
||||
|
|
|
@ -103,6 +103,7 @@ methods.
|
|||
\end{funcdesc}
|
||||
|
||||
\subsection{Example}
|
||||
\nodename{HTTP Example}
|
||||
|
||||
Here is an example session:
|
||||
|
||||
|
|
|
@ -43,6 +43,7 @@ I'd appreciate the feedback.
|
|||
|
||||
|
||||
\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
|
||||
|
@ -54,6 +55,7 @@ examine the results of a profile operation.
|
|||
|
||||
|
||||
\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
|
||||
|
@ -209,6 +211,7 @@ manual, or guess what the following functions do:
|
|||
|
||||
|
||||
\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
|
||||
|
@ -604,7 +607,8 @@ performance section, and there is no reason to use a variable lookup
|
|||
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
|
||||
|
|
|
@ -21,6 +21,7 @@ For a complete description of STDWIN please refer to the documentation
|
|||
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:
|
||||
|
||||
|
@ -735,7 +736,7 @@ Discard the text-edit object. It should not be used again.
|
|||
\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
|
||||
|
|
|
@ -206,6 +206,7 @@ See the section on built-in functions for an exact definition.
|
|||
% 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
|
||||
|
@ -483,6 +484,7 @@ defines \code{\var{m}.a} to be \code{1}, but you can't write \code{\var{m}.__dic
|
|||
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.)
|
||||
|
||||
|
|
|
@ -1,4 +1,5 @@
|
|||
\chapter{THE INTERNET AND THE WORLD-WIDE WEB}
|
||||
\nodename{Internet and WWW}
|
||||
\index{WWW}
|
||||
\index{Internet}
|
||||
\index{World-Wide Web}
|
||||
|
|
Loading…
Reference in New Issue