From c16a142e17c33cb3f3fa17e980732fc0141d9c16 Mon Sep 17 00:00:00 2001
From: deraadt <>
Date: Sat, 5 Jun 1999 19:29:43 +0000
Subject: stronger suggest

---
 src/lib/libc/net/inet.3 | 15 +++++++++------
 1 file 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 @@
-.\"	$OpenBSD: inet.3,v 1.6 1999/05/25 13:06:45 aaron Exp $
+.\"	$OpenBSD: inet.3,v 1.7 1999/06/05 19:29:43 deraadt Exp $
 .\"	$NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $
 .\"
 .\" Copyright (c) 1983, 1990, 1991, 1993
@@ -303,9 +303,16 @@ The value
 (0xffffffff) is a valid broadcast address, but
 .Fn inet_addr
 cannot return that value without indicating failure.
+Also,
+.Fn inet_addr
+should have been designed to return a
+.Fa "struct in_addr" .
 The newer
 .Fn inet_aton
-function does not share this problem.
+function does not share these problems, and almost all existing code
+should be modified to use
+.Fn inet_aton
+instead.
 .Pp
 The problem of host byte ordering versus network byte ordering is
 confusing.
@@ -313,7 +320,3 @@ confusing.
 The string returned by
 .Fn inet_ntoa
 resides in a static memory area.
-.Pp
-.Fn inet_addr
-should return a
-.Fa "struct in_addr" .
-- 
cgit v1.2.3-55-g6feb