summaryrefslogtreecommitdiff
path: root/manual/socket.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-01-28 22:09:12 +0000
committerUlrich Drepper <drepper@redhat.com>1999-01-28 22:09:12 +0000
commit8163845fdab02ba1943b608b635873cee50df676 (patch)
tree06a81f336e654c64ba7282356b4c79d5c91a4589 /manual/socket.texi
parent1f749a3ba208fd615b5524eb6bbeea212211ff1a (diff)
Update.
1999-01-28 David S. Miller <davem@redhat.com> * sysdeps/sparc/sparc32/__longjmp.S: Rewrite without bogus sanity checks and aborts, to make longjmp based thread schemes work again.
Diffstat (limited to 'manual/socket.texi')
-rw-r--r--manual/socket.texi17
1 files changed, 8 insertions, 9 deletions
diff --git a/manual/socket.texi b/manual/socket.texi
index 4de5b9cd56..5f31dd47d8 100644
--- a/manual/socket.texi
+++ b/manual/socket.texi
@@ -140,18 +140,17 @@ bits wide and so a de-factor standard required 32 bit variables. This
is important since references to variables of this type are passed to
the kernel.
-But now the POSIX people came and unified the interface with their words
+But then the POSIX people came and unified the interface with the words
"all size values are of type @code{size_t}". But on 64 bit machines
-@code{size_t} is 64 bits wide and so variable references are not anymore
+@code{size_t} is 64 bits wide, and so variable references are not anymore
possible.
-A solution is provided by the Unix98 specification which finally
-introduces a type @code{socklen_t}. This type is used in all of the
-cases that were previously changed to use @code{size_t}. The only
-requirement of this type is that it is an unsigned type of at least 32
-bits. Therefore, implementations which require references to 32 bit
-variables be passed can be as happy as implementations which use right
-from the start 64 bit values.
+The Unix98 specification provides a solution by introducing a type
+@code{socklen_t}. This type is used in all of the cases that POSIX
+changed to use @code{size_t}. The only requirement of this type is that
+it be an unsigned type of at least 32 bits. Therefore, implementations
+which require that references to 32 bit variables be passed can be as
+happy as implementations which use 64 bit values.
@node Communication Styles