diff options
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/lib/libsocket.tex | 2 | ||||
| -rw-r--r-- | Doc/libsocket.tex | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libsocket.tex b/Doc/lib/libsocket.tex index 3743100..618c523 100644 --- a/Doc/lib/libsocket.tex +++ b/Doc/lib/libsocket.tex @@ -17,7 +17,7 @@ The Python interface is a straightforward transliteration of the \UNIX{} system call and library interface for sockets to Python's object-oriented style: the \code{socket()} function returns a \dfn{socket object} whose methods implement the various socket system -calls. Parameter types are somewhat higer-level than in the C +calls. Parameter types are somewhat higher-level than in the C interface: as with \code{read()} and \code{write()} operations on Python files, buffer allocation on receive operations is automatic, and buffer length is implicit on send operations. diff --git a/Doc/libsocket.tex b/Doc/libsocket.tex index 3743100..618c523 100644 --- a/Doc/libsocket.tex +++ b/Doc/libsocket.tex @@ -17,7 +17,7 @@ The Python interface is a straightforward transliteration of the \UNIX{} system call and library interface for sockets to Python's object-oriented style: the \code{socket()} function returns a \dfn{socket object} whose methods implement the various socket system -calls. Parameter types are somewhat higer-level than in the C +calls. Parameter types are somewhat higher-level than in the C interface: as with \code{read()} and \code{write()} operations on Python files, buffer allocation on receive operations is automatic, and buffer length is implicit on send operations. |