@@ -187,14 +187,14 @@ \subsection{Socket Object Methods}
187187
188188\begin {funcdesc }{getsockopt}{level\, optname\, buflen}
189189Return the value of the given socket option (see the \UNIX {} man page
190- {\it getsockopt}(2)). The needed symbolic constants are defined in module
191- SOCKET. If the optional third argument is absent, an integer option
192- is assumed and its integer value is returned by the function. If
193- \var {buflen} is present, it specifies the maximum length of the buffer used
194- to receive the option in, and this buffer is returned as a string.
195- It's up to the caller to decode the contents of the buffer (see the
196- optional built-in module \code {struct} for a way to decode C structures
197- encoded as strings).
190+ {\it getsockopt}(2)). The needed symbolic constants are defined in
191+ the \code {socket} module ( \code {SO_*} etc.). If the optional third
192+ argument is absent, an integer option is assumed and its integer value
193+ is returned by the function. If \var {buflen} is present, it specifies
194+ the maximum length of the buffer used to receive the option in, and
195+ this buffer is returned as a string. It's up to the caller to decode
196+ the contents of the buffer (see the optional built-in module
197+ \code {struct} for a way to decode C structures encoded as strings).
198198\end {funcdesc }
199199
200200\begin {funcdesc }{listen}{backlog}
@@ -250,10 +250,11 @@ \subsection{Socket Object Methods}
250250
251251\begin {funcdesc }{setsockopt}{level\, optname\, value}
252252Set the value of the given socket option (see the \UNIX {} man page
253- {\it setsockopt}(2)). The needed symbolic constants are defined in module
254- \code {SOCKET}. The value can be an integer or a string representing a
255- buffer. In the latter case it is up to the caller to ensure that the
256- string contains the proper bits (see the optional built-in module
253+ {\it setsockopt}(2)). The needed symbolic constants are defined in
254+ the \code {socket} module (\code {SO_*} etc.). The value can be an
255+ integer or a string representing a buffer. In the latter case it is
256+ up to the caller to ensure that the string contains the proper bits
257+ (see the optional built-in module
257258\code {struct} for a way to encode C structures as strings).
258259\end {funcdesc }
259260
0 commit comments