summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--src/lib/libc/net/inet.315
1 files changed, 9 insertions, 6 deletions
diff --git a/src/lib/libc/net/inet.3 b/src/lib/libc/net/inet.3
index a9da73db3a..d29f3160aa 100644
--- a/src/lib/libc/net/inet.3
+++ b/src/lib/libc/net/inet.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: inet.3,v 1.6 1999/05/25 13:06:45 aaron Exp $ 1.\" $OpenBSD: inet.3,v 1.7 1999/06/05 19:29:43 deraadt Exp $
2.\" $NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $ 2.\" $NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $
3.\" 3.\"
4.\" Copyright (c) 1983, 1990, 1991, 1993 4.\" Copyright (c) 1983, 1990, 1991, 1993
@@ -303,9 +303,16 @@ The value
303(0xffffffff) is a valid broadcast address, but 303(0xffffffff) is a valid broadcast address, but
304.Fn inet_addr 304.Fn inet_addr
305cannot return that value without indicating failure. 305cannot return that value without indicating failure.
306Also,
307.Fn inet_addr
308should have been designed to return a
309.Fa "struct in_addr" .
306The newer 310The newer
307.Fn inet_aton 311.Fn inet_aton
308function does not share this problem. 312function does not share these problems, and almost all existing code
313should be modified to use
314.Fn inet_aton
315instead.
309.Pp 316.Pp
310The problem of host byte ordering versus network byte ordering is 317The problem of host byte ordering versus network byte ordering is
311confusing. 318confusing.
@@ -313,7 +320,3 @@ confusing.
313The string returned by 320The string returned by
314.Fn inet_ntoa 321.Fn inet_ntoa
315resides in a static memory area. 322resides in a static memory area.
316.Pp
317.Fn inet_addr
318should return a
319.Fa "struct in_addr" .