From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: ip(2) man page: return code of parseip() and parsemaskip()
Date: Fri, 20 Oct 2006 09:44:27 -0400 [thread overview]
Message-ID: <ee9e417a0610200644o289c7ef2x91dbef158e915c96@mail.gmail.com> (raw)
In-Reply-To: <9ce16737e7bc48959b13dcce37e7560d@coraid.com>
The man page lies. There is no way to tell using
those functions whether you have parsed a valid
address.
::ffff:192.168.0.1 is *not* an IPv4 address, syntactically.
IPv4 addresses don't have colons and hexadecimal in them.
It may be an IPv6 address that is semantically equivalent
to an IPv4 address, but parseip is just a poor little parser.
Russ
next prev parent reply other threads:[~2006-10-20 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 9:04 [9fans] " Gabriel Diaz
2006-10-20 9:48 ` [9fans] " Gabriel Diaz
2006-10-20 12:56 ` erik quanstrom
2006-10-20 13:44 ` Russ Cox [this message]
2006-10-20 13:56 ` erik quanstrom
2006-10-20 14:38 ` Russ Cox
2006-10-20 15:20 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee9e417a0610200644o289c7ef2x91dbef158e915c96@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).