From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Initial SCTP support for the upcoming 1.6.5 release
Date: Fri, 20 Aug 2004 11:13:32 +1000 [thread overview]
Message-ID: <87llgabohv.fsf@zip.com.au> (raw)
In-Reply-To: <60ADA546-F20E-11D8-A47A-000D932C78D8@lurchi.franken.de> (Michael Tuexen's message of "Thu, 19 Aug 2004 20:34:17 +0200")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>
> The argument, to use a function like getprotobyname
> to perform a lookup in /etc/protocols, is not valid in my opinion.
> The reason is, that besides I have not seen that, that the
> constants above are defined in /usr/include/netinet/in.h and
> are used.
I don't want to go against the advice of the GNU/Linux man page. It's
pretty explicit.
> So if, a system (I do not know of any such system),
> uses a different number for TCP, this number will not only be in
> /etc/protocols, but also in /usr/include/netinet/in.h. A different
> story are port numbers. They can (and should) be looked up in
> /etc/services.
> There are no constants describing the port number for an echo server...
Well I guess both protocol and service numbers for standard stuff are
constants. I don't know why one reads a file instead of just putting
numbers in a program. Maybe it dates right back to a time when such
things were still in flux. Or maybe the theory is to avoid numbers
hard coded in programs (though strings hard coded aren't much better
:-).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-20 1:13 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
2004-08-17 23:46 ` Kevin Ryde
2004-08-19 18:34 ` Michael Tuexen
2004-08-20 1:13 ` Kevin Ryde [this message]
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=87llgabohv.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).