traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Consistency: "{\it ...}" ==> "\emph{...}"

This commit is contained in:
Fred Drake 1998-01-20 04:54:23 +00:00
parent c520b695fe
commit 9eb5e5097e
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/lib/libsocket.tex
View File

@ -242,7 +242,7 @@ see above.)
\begin{funcdesc}{getsockopt}{level\, optname\optional{\, buflen}} \begin{funcdesc}{getsockopt}{level\, optname\optional{\, buflen}}
Return the value of the given socket option (see the \UNIX{} man page Return the value of the given socket option (see the \UNIX{} man page
{\it getsockopt}(2)). The needed symbolic constants (\code{SO_*} etc.) \emph{getsockopt}(2)). The needed symbolic constants (\code{SO_*} etc.)
are defined in this module. If \var{buflen} are defined in this module. If \var{buflen}
is absent, an integer option is assumed and its integer value is absent, an integer option is assumed and its integer value
is returned by the function. If \var{buflen} is present, it specifies is returned by the function. If \var{buflen} is present, it specifies
@ -310,7 +310,7 @@ raised; in blocking mode, the calls block until they can proceed.
\begin{funcdesc}{setsockopt}{level\, optname\, value} \begin{funcdesc}{setsockopt}{level\, optname\, value}
Set the value of the given socket option (see the \UNIX{} man page Set the value of the given socket option (see the \UNIX{} man page
{\it setsockopt}(2)). The needed symbolic constants are defined in \emph{setsockopt}(2)). The needed symbolic constants are defined in
the \code{socket} module (\code{SO_*} etc.). The value can be an the \code{socket} module (\code{SO_*} etc.). The value can be an
integer or a string representing a buffer. In the latter case it is integer or a string representing a buffer. In the latter case it is
up to the caller to ensure that the string contains the proper bits up to the caller to ensure that the string contains the proper bits

4
Doc/libsocket.tex
View File

@ -242,7 +242,7 @@ see above.)
\begin{funcdesc}{getsockopt}{level\, optname\optional{\, buflen}} \begin{funcdesc}{getsockopt}{level\, optname\optional{\, buflen}}
Return the value of the given socket option (see the \UNIX{} man page Return the value of the given socket option (see the \UNIX{} man page
{\it getsockopt}(2)). The needed symbolic constants (\code{SO_*} etc.) \emph{getsockopt}(2)). The needed symbolic constants (\code{SO_*} etc.)
are defined in this module. If \var{buflen} are defined in this module. If \var{buflen}
is absent, an integer option is assumed and its integer value is absent, an integer option is assumed and its integer value
is returned by the function. If \var{buflen} is present, it specifies is returned by the function. If \var{buflen} is present, it specifies
@ -310,7 +310,7 @@ raised; in blocking mode, the calls block until they can proceed.
\begin{funcdesc}{setsockopt}{level\, optname\, value} \begin{funcdesc}{setsockopt}{level\, optname\, value}
Set the value of the given socket option (see the \UNIX{} man page Set the value of the given socket option (see the \UNIX{} man page
{\it setsockopt}(2)). The needed symbolic constants are defined in \emph{setsockopt}(2)). The needed symbolic constants are defined in
the \code{socket} module (\code{SO_*} etc.). The value can be an the \code{socket} module (\code{SO_*} etc.). The value can be an
integer or a string representing a buffer. In the latter case it is integer or a string representing a buffer. In the latter case it is
up to the caller to ensure that the string contains the proper bits up to the caller to ensure that the string contains the proper bits