From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: binary-port?
Date: Sat, 23 Apr 2011 00:28:03 +0200 [thread overview]
Message-ID: <871v0tudjg.fsf@gnu.org> (raw)
Hello,
I just pushed 96128014bfaabe9e123c4f4928ce4c20427eaa53, which makes
‘binary-port?’ deterministic for ports intended to be binary.
However, I’m wondering whether we should not just squarely do away with
the binary/textual distinction, and just write:
(define (binary-port? p) #t)
What do people with experience with pure R6RS code think? Is the
distinction actually used, and how?
Thanks,
Ludo’.
next reply other threads:[~2011-04-22 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 22:28 Ludovic Courtès [this message]
2011-04-23 1:48 ` binary-port? Andreas Rottmann
2011-04-23 19:56 ` binary-port? Ludovic Courtès
2011-04-24 6:39 ` binary-port? Marco Maggi
2011-04-24 13:03 ` binary-port? Ludovic Courtès
2011-04-25 11:55 ` binary-port? Andreas Rottmann
2011-04-25 14:08 ` binary-port? Ludovic Courtès
2011-04-25 14:20 ` binary-port? Andy Wingo
2011-04-26 0:16 ` binary-port? Andreas Rottmann
2011-04-26 15:00 ` binary-port? 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=871v0tudjg.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).