From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: guile-devel@gnu.org
Subject: Re: Initial SCTP support for the upcoming 1.6.5 release
Date: Mon, 16 Aug 2004 12:42:16 +0200 [thread overview]
Message-ID: <F10A1D84-EF70-11D8-B940-000D932C78D8@lurchi.franken.de> (raw)
In-Reply-To: <87657jc3v2.fsf@zip.com.au>
Dear all,
see my comments below.
Best regards
Michael
On Aug 16, 2004, at 2:40 AM, Kevin Ryde wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>>
>> Is there a possibility to include
>>
>> #ifdef SOCK_SEQPACKET
>> scm_c_define ("SOCK_SEQPACKET", SCM_MAKINUM (SOCK_SEQPACKET));
>> #endif
>
> I imagine so.
>
Great.
>> /* protocol numbers */
>> #ifdef IPPROTO_SCTP
>> scm_c_define ("IPPROTO_SCTP", SCM_MAKINUM (IPPROTO_SCTP));
>> #endif
>>
>> #ifdef IPPROTO_TCP
>> scm_c_define ("IPPROTO_TCP", SCM_MAKINUM (IPPROTO_TCP));
>> #endif
>>
>> #ifdef IPPROTO_UDP
>> scm_c_define ("IPPROTO_UDP", SCM_MAKINUM (IPPROTO_UDP));
>> #endif
>
> No, I think "man 5 protocols" advises using /etc/protocols, not hard
> coding numbers.
Hmm. I have not seen code with does that for the last argument
of a socket() call. Normally 0 is used, which means 'select whatever
is appropiate'. For port numbers using a function call is common,
especially if the user can specify a name on the command line.
Please note that these numbers are IANA registered numbers
and you do not have a choice.
But it is your decision to include it or not.
>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-16 10:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:26 Initial SCTP support for the upcoming 1.6.5 release Michael Tuexen
2004-08-11 12:29 ` Michael Tuexen
2004-08-13 13:40 ` Marius Vollmer
2004-08-13 20:27 ` Michael Tuexen
2004-08-24 14:15 ` Marius Vollmer
2004-08-24 17:35 ` Michael Tuexen
2004-09-08 15:03 ` Marius Vollmer
2004-09-08 15:34 ` Michael Tuexen
2004-08-14 9:59 ` Michael Tuexen
2004-08-16 0:40 ` Kevin Ryde
2004-08-16 10:42 ` Michael Tuexen [this message]
2004-08-17 23:46 ` Kevin Ryde
2004-08-19 18:34 ` Michael Tuexen
2004-08-20 1:13 ` Kevin Ryde
2004-08-20 7:57 ` Michael Tuexen
2004-08-16 17:02 ` Michael Tuexen
2004-08-16 18:44 ` Rob Browning
2004-08-20 18:18 ` Michael Tuexen
2004-08-23 0:58 ` Kevin Ryde
2004-08-23 19:54 ` Michael Tuexen
2004-08-24 0:57 ` Kevin Ryde
2004-08-24 11:27 ` Michael Tuexen
2004-08-24 12:46 ` Michael Tuexen
2004-08-24 14:24 ` Marius Vollmer
2004-08-24 18:22 ` Michael Tuexen
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=F10A1D84-EF70-11D8-B940-000D932C78D8@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.de \
--cc=guile-devel@gnu.org \
/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).