From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Making custom binary input ports unbuffered
Date: Sat, 18 Jan 2014 22:57:06 +0100 [thread overview]
Message-ID: <87fvolnebx.fsf@gnu.org> (raw)
In-Reply-To: 8761pjjzvm.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) skribis:
> So here’s a version that adds a ‘setvbuf’ method to scm_t_port_internal,
> and uses that to implement CBIP buffering. CBIPs remain fully buffered
> by default (after more thoughts I considered that this conservative
> approach was more reasonable and acceptable if documented.)
Pushed to ‘stable-2.0’.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-01-18 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 23:00 Making custom binary input ports unbuffered Ludovic Courtès
2014-01-15 5:43 ` Mark H Weaver
2014-01-15 11:48 ` Ludovic Courtès
2014-01-15 22:51 ` Ludovic Courtès
2014-01-16 0:15 ` Mark H Weaver
2014-01-16 23:00 ` Ludovic Courtès
2014-01-18 21:57 ` Ludovic Courtès [this message]
2014-01-21 7:41 ` Mark H Weaver
2014-01-21 10:50 ` Ludovic Courtès
2014-01-21 14:46 ` Mark H Weaver
2014-01-21 17:37 ` Ludovic Courtès
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=87fvolnebx.fsf@gnu.org \
--to=ludo@gnu.org \
--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).