From: Andy Wingo <wingo@pobox.com>
To: "Göran Weinholt" <goran@weinholt.se>
Cc: 15123-done@debbugs.gnu.org
Subject: bug#15123: Missing R6RS io port exports
Date: Tue, 21 Jun 2016 11:30:39 +0200 [thread overview]
Message-ID: <87vb123n40.fsf@pobox.com> (raw)
In-Reply-To: <87ob8vurfj.fsf@industria.weinholt.se> ("Göran Weinholt"'s message of "Sun, 18 Aug 2013 14:14:24 +0200")
On Sun 18 Aug 2013 14:14, Göran Weinholt <goran@weinholt.se> writes:
> Hello schemers,
>
> these identifiers are not exported by the (rnrs) library:
>
> &i/o-decoding
> i/o-decoding-error?
> &i/o-encoding
> i/o-encoding-error-char
> i/o-encoding-error?
> make-i/o-decoding-error
> make-i/o-encoding-error
> output-port-buffer-mode
Fixed, thanks.
> Additionally these identifiers are not exported by (rnrs io ports):
>
> &i/o-decoding
> &i/o-encoding
> output-port-buffer-mode
Fixed as well.
> For completeness I will also mention that these exports are missing from
> both libraries (I assume because their implementation is non-trivial):
>
> make-custom-binary-input/output-port
> make-custom-textual-input-port
> make-custom-textual-input/output-port
> bytevector->string
> string->bytevector
I added implementations of bytevector->string and string->bytevector.
Custom textual and binary ports are still a TODO, but it's good enough
to close this bug.
Cheers,
Andy
prev parent reply other threads:[~2016-06-21 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 12:14 bug#15123: Missing R6RS io port exports Göran Weinholt
2016-06-21 9:30 ` Andy Wingo [this message]
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=87vb123n40.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=15123-done@debbugs.gnu.org \
--cc=goran@weinholt.se \
/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).