From fc4de7058d30387e302147c6131f85440987fe5c Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Sun, 24 Oct 1999 23:55:16 +0000 Subject: [PATCH] Update. 1999-10-20 Andreas Jaeger * manual/socket.texi (Address Formats): Describe usage of AF_UNIX versus AF_LOCAL. Patch by Robert Bihlmeyer . --- ChangeLog | 6 ++++++ manual/socket.texi | 10 +++++++--- 2 files changed, 13 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index a750df3..5f7b4f7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +1999-10-20 Andreas Jaeger + + * manual/socket.texi (Address Formats): Describe usage of AF_UNIX + versus AF_LOCAL. + Patch by Robert Bihlmeyer . + 1999-10-24 Ulrich Drepper * math/libm-test.inc: Disable some boundary case tests for inline diff --git a/manual/socket.texi b/manual/socket.texi index 0c8fef3f..ab94f29 100644 --- a/manual/socket.texi +++ b/manual/socket.texi @@ -335,11 +335,15 @@ This designates the address format that goes with the local namespace. Details}, for information about this address format. @comment sys/socket.h -@comment BSD +@comment BSD, Unix98 @item AF_UNIX @vindex AF_UNIX -This is a synonym for @code{AF_LOCAL}, for compatibility. -(@code{PF_UNIX} is likewise a synonym for @code{PF_LOCAL}.) +This is a synonym for @code{AF_LOCAL}. Although @code{AF_LOCAL} is +mandated by POSIX.1g, @code{AF_UNIX} is portable to more systems. +@code{AF_UNIX} was the traditional name stemming from BSD, so even most +POSIX systems support it. It is also the name of choice in the Unix98 +specification. (The same is true for @code{PF_UNIX} +vs. @code{PF_LOCAL}). @comment sys/socket.h @comment GNU -- 2.7.4