Duh. Back out most of my previous commit. It was mostly covered in the
STANDARDS section of the page. Add one remark there about inet_pton(3) only understanding decimal values (in contrast to inet_aton(3) and friends who are happy with 0ac.020.25 for 172.16.0.25). Caught by: ru MFC after: 2 days
This commit is contained in:
parent
ac65a69a07
commit
e377442703
@ -203,14 +203,6 @@ hexadecimal; otherwise, a leading 0 implies octal;
|
||||
otherwise, the number is interpreted as decimal).
|
||||
.Pp
|
||||
The
|
||||
.Fn inet_pton
|
||||
function only understands Internet addresses written as dotted quads.
|
||||
Each
|
||||
.Dq part
|
||||
may only contain numeric characters and is always interpreted as a
|
||||
decimal value.
|
||||
.Pp
|
||||
The
|
||||
.Fn inet_aton
|
||||
and
|
||||
.Fn inet_ntoa
|
||||
@ -253,7 +245,7 @@ functions conform to
|
||||
Note that
|
||||
.Fn inet_pton
|
||||
does not accept 1-, 2-, or 3-part dotted addresses; all four parts
|
||||
must be specified.
|
||||
must be specified and are interpreted only as decimal values.
|
||||
This is a narrower input set than that accepted by
|
||||
.Fn inet_aton .
|
||||
.Sh HISTORY
|
||||
|
Loading…
Reference in New Issue
Block a user