unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Göran Weinholt" <goran@weinholt.se>
To: 15123@debbugs.gnu.org
Subject: bug#15123: Missing R6RS io port exports
Date: Sun, 18 Aug 2013 14:14:24 +0200	[thread overview]
Message-ID: <87ob8vurfj.fsf@industria.weinholt.se> (raw)

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

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

As you can see:

scheme@(guile-user)> (import (rnrs eval))
scheme@(guile-user)> (environment '&i/o-decoding-error (environment '(rnrs)))
ice-9/eval.scm:411:25: In procedure eval:
ice-9/eval.scm:411:25: Syntax error:
unknown location: source expression failed to match any pattern in form &i/o-decoding-error

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
scheme@(#{ g365}#) [1]> 

(Btw, what's up with the gensym in that prompt?)

Additionally these identifiers are not exported by (rnrs io ports):

  &i/o-decoding
  &i/o-encoding
  output-port-buffer-mode

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

The last two are already reported in bug #14109.

Tested with GNU Guile 2.0.9.71-8d5d04.

Regards,

-- 
Göran Weinholt <goran@weinholt.se>
"I'm the kinda guy that if I can't figure it out on my own, then I'm
just not gonna waste my time doing it." -- David Letterman

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

             reply	other threads:[~2013-08-18 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 12:14 Göran Weinholt [this message]
2016-06-21  9:30 ` bug#15123: Missing R6RS io port exports Andy Wingo

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=87ob8vurfj.fsf@industria.weinholt.se \
    --to=goran@weinholt.se \
    --cc=15123@debbugs.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).