From: Kevin Ryde <user42@zip.com.au>
Subject: doco socket
Date: Tue, 26 Aug 2003 08:01:19 +1000 [thread overview]
Message-ID: <87ptitcs7k.fsf@zip.com.au> (raw)
* posix.texi (Network Sockets and Communication): In socket, use
@defvar for protocol variables, cross reference for getprotobyname,
note it's usually connect and accept that establishes communication.
- Scheme Procedure: socket family style proto
- C Function: scm_socket (family, style, proto)
Return a new socket port of the type specified by FAMILY, STYLE
and PROTO. All three parameters are integers. The possible
values for FAMILY are as follows, where supported by the system
- Variable: PF_UNIX
- Variable: PF_INET
- Variable: PF_INET6
The possible values for STYLE are as follows, again where
supported by the system,
- Variable: SOCK_STREAM
- Variable: SOCK_DGRAM
- Variable: SOCK_RAW
PROTO can be obtained from a protocol name using `getprotobyname'
(*note Network Databases::). A value of zero specifies the
default protocol, which is usually right.
A socket cannot by used for communication until it has been
connected somewhere, usually with either `connect' or `accept'
below.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-08-25 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ptitcs7k.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).