From: Kevin Ryde <user42@zip.com.au>
Subject: doco PIPE_BUF
Date: Tue, 26 Aug 2003 07:59:48 +1000 [thread overview]
Message-ID: <877k51e6uj.fsf@zip.com.au> (raw)
A bit of a tweak to the layout,
* posix.texi (Ports and File Descriptors): Use @defvar for PIPE_BUF,
cross reference glibc manual on atomicity.
- Scheme Procedure: pipe
- C Function: scm_pipe ()
Return a newly created pipe: a pair of ports which are linked
together on the local machine. The CAR is the input port and the
CDR is the output port. Data written (and flushed) to the output
port can be read from the input port. Pipes are commonly used for
communication with a newly forked child process. The need to
flush the output port can be avoided by making it unbuffered using
`setvbuf'.
- Variable: PIPE_BUF
A write of up to `PIPE_BUF' bytes to a pipe is atomic, meaning
when done it goes into the pipe instantaneously and as a
contiguous block (*note Atomicity of Pipe I/O: (libc)Pipe
Atomicity.).
Note that the output port is likely to block if too much data has
been written but not yet read from the input port. Typically the
capacity is `PIPE_BUF' bytes.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-08-25 21:59 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=877k51e6uj.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).