unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Roel Janssen <roel@gnu.org>
To: dsmich@roadrunner.com
Cc: 44371-close@debbugs.gnu.org
Subject: bug#44371: Missing 'get-bytevector-some!' in Guile 2.2
Date: Sun, 01 Nov 2020 22:39:01 +0100	[thread overview]
Message-ID: <8d9316d34afa0bc9ec361d3988dd0980d94f67e7.camel@gnu.org> (raw)
In-Reply-To: <59ea936a03fa51d17b14d062ac64843727ddd23d@webmail>

On Sun, 2020-11-01 at 18:40 +0000, dsmich@roadrunner.com wrote:
> 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

Thanks Dale, I should've looked more carefully.

Closing this bug report.

Kind regards,
Roel Janssen






      reply	other threads:[~2020-11-01 21:39 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
2020-11-01 21:39   ` Roel Janssen [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=8d9316d34afa0bc9ec361d3988dd0980d94f67e7.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=44371-close@debbugs.gnu.org \
    --cc=dsmich@roadrunner.com \
    /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).