From: Greg Troxel <gdt@ir.bbn.com>
Subject: Re: doc getsockopt, setsockopt
Date: 02 Oct 2005 19:09:03 -0400 [thread overview]
Message-ID: <rmiirwfldo0.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87k6gyi29b.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> Greg Troxel <gdt@ir.bbn.com> writes:
>
> I'd noticed in the past the gnu/linux "man 5 protocols" says to use
> /etc/protocols instead of numbers like IPPROTO, but what posix says
> must trump that.
I think getprotobyname is supposed to return IANA-allocated protocol
numbers, so while 'posix rulz' is a great attitude and one I share,
there's no real conflict.
> > NetBSD's Linux compatibility code indicates that SOL_IP is 0, but has
> > a comment that these values can vary by architecture
>
> That should be ok, we don't care about the actual values as long as
> the constants are right.
True; I was just trying to point out the complexity I found in case it
mattered later.
> Do you need to know about host vs network byte order to get it
> through? That would be something to note.
Yes, but I think it's the same as all other bind/etc. calls.
I just pass the result of
(define *ssp-addr* (inet-aton "224.0.x.y")) ;not registered
so it's host order, like all the other calls. Docs for bind,
connect and send don't mention this though.
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-02 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 21:31 doc getsockopt, setsockopt Kevin Ryde
2005-09-30 15:58 ` Greg Troxel
2005-09-30 23:06 ` Kevin Ryde
2005-10-02 23:09 ` Greg Troxel [this message]
2005-10-03 1:10 ` Kevin Ryde
2005-10-03 23:46 ` Greg Troxel
2005-10-11 22:54 ` Kevin Ryde
2005-10-12 14:30 ` Greg Troxel
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmiirwfldo0.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).