diff options
| author | deraadt <> | 1999-06-05 19:29:43 +0000 |
|---|---|---|
| committer | deraadt <> | 1999-06-05 19:29:43 +0000 |
| commit | c16a142e17c33cb3f3fa17e980732fc0141d9c16 (patch) | |
| tree | c305a9a2a328996d0cc7767201290ca639a1cc80 /src/lib/libc/net | |
| parent | 64e5679419440e1ce0502f4372226d92fcff26b1 (diff) | |
| download | openbsd-c16a142e17c33cb3f3fa17e980732fc0141d9c16.tar.gz openbsd-c16a142e17c33cb3f3fa17e980732fc0141d9c16.tar.bz2 openbsd-c16a142e17c33cb3f3fa17e980732fc0141d9c16.zip | |
stronger suggest
Diffstat (limited to 'src/lib/libc/net')
| -rw-r--r-- | src/lib/libc/net/inet.3 | 15 |
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 |
| 305 | cannot return that value without indicating failure. | 305 | cannot return that value without indicating failure. |
| 306 | Also, | ||
| 307 | .Fn inet_addr | ||
| 308 | should have been designed to return a | ||
| 309 | .Fa "struct in_addr" . | ||
| 306 | The newer | 310 | The newer |
| 307 | .Fn inet_aton | 311 | .Fn inet_aton |
| 308 | function does not share this problem. | 312 | function does not share these problems, and almost all existing code |
| 313 | should be modified to use | ||
| 314 | .Fn inet_aton | ||
| 315 | instead. | ||
| 309 | .Pp | 316 | .Pp |
| 310 | The problem of host byte ordering versus network byte ordering is | 317 | The problem of host byte ordering versus network byte ordering is |
| 311 | confusing. | 318 | confusing. |
| @@ -313,7 +320,3 @@ confusing. | |||
| 313 | The string returned by | 320 | The string returned by |
| 314 | .Fn inet_ntoa | 321 | .Fn inet_ntoa |
| 315 | resides in a static memory area. | 322 | resides in a static memory area. |
| 316 | .Pp | ||
| 317 | .Fn inet_addr | ||
| 318 | should return a | ||
| 319 | .Fa "struct in_addr" . | ||
