unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 49363@debbugs.gnu.org
Subject: bug#49363: eof-object? is not exported from (ice-9 binary-ports)
Date: Sat, 03 Jul 2021 22:24:10 +0200	[thread overview]
Message-ID: <8947442579e3360304579b254f66f313978dd405.camel@telenet.be> (raw)

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

According to the manual:

6.12.2 Binary I/O
-----------------

[...]
   To use these routines, first include the binary I/O module:

     (use-modules (ice-9 binary-ports))

[...]
   The end-of-file object is unlike any other kind of object: it’s not a
pair, a symbol, or anything else.  To check if a value is the
end-of-file object, use the ‘eof-object?’ predicate.

 -- Scheme Procedure: eof-object? x
 -- C Function: scm_eof_object_p (x)
     Return ‘#t’ if X is an end-of-file object, or ‘#f’ otherwise.

However, eof-object? is not exported by (ice-9 binary-ports):

scheme@(guile-user)> (@ (ice-9 binary-ports) eof-object?)
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Unbound variable: eof-object?

But it is imported from (ice-9 ports):

scheme@(guile-user) [1]> (@ (ice-9 ports) eof-object?)
$1 = #<procedure eof-object? (_)>

Could an appropriate export be added to (ice-9 binary-ports)?
Or the manual adjusted to note you need to import (ice-9 ports)
to get eof-object?

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

             reply	other threads:[~2021-07-03 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 20:24 Maxime Devos [this message]
2021-07-04  5:54 ` bug#49363: eof-object? is not exported from (ice-9 binary-ports) Linus Björnstam
2021-07-04 11:48   ` Maxime Devos

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=8947442579e3360304579b254f66f313978dd405.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=49363@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).