From: dsmich@roadrunner.com
To: "'Roel Janssen'" <roel@gnu.org>
Cc: "'44371@debbugs.gnu.org'" <44371@debbugs.gnu.org>
Subject: bug#44371: Missing 'get-bytevector-some!' in Guile 2.2
Date: Sun, 01 Nov 2020 18:40:49 +0000 [thread overview]
Message-ID: <59ea936a03fa51d17b14d062ac64843727ddd23d@webmail> (raw)
In-Reply-To: <af6cd11ed755bbe19081ef1c3aafad64bfc80479.camel@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
You have 2.2.4. It was added in 2.2.5.
From the NEWS file:
Changes in 2.2.5 (since 2.2.4):
....
** New 'get-bytevector-some!' I/O primitive.
-Dale
-----------------------------------------From: "Roel Janssen"
To: 44371@debbugs.gnu.org
Cc:
Sent: Sunday November 1 2020 9:42:07AM
Subject: bug#44371: Missing 'get-bytevector-some!' in Guile 2.2
Dear Guix,
I installed guile-2.2 on Debian 10.6 and I seem to missing the "get-
bytevector-some!" procedure from "(ice-9 binary-ports)":
----------
# guile
GNU Guile 2.2.4
Copyright (C) 1995-2017 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)> ,use (ice-9 binary-ports)
scheme@(guile-user)> get-bytevector-some!
;;; : warning: possibly unbound variable `get-
bytevector-some!'
ERROR: In procedure module-lookup: Unbound variable: get-bytevector-
some!
Entering a new prompt. Type `,bt' for a backtrace or `,q' to
continue.
scheme@(guile-user) [1]> ,q
scheme@(guile-user)> get-bytevector-some
$1 = #
----------
Kind regards,
Roel Janssen
[-- Attachment #2: Type: text/html, Size: 1570 bytes --]
next prev parent reply other threads:[~2020-11-01 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 14:41 bug#44371: Missing 'get-bytevector-some!' in Guile 2.2 Roel Janssen
2020-11-01 18:40 ` dsmich [this message]
2020-11-01 21:39 ` Roel Janssen
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=59ea936a03fa51d17b14d062ac64843727ddd23d@webmail \
--to=dsmich@roadrunner.com \
--cc=44371@debbugs.gnu.org \
--cc=roel@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).