From: Mark H Weaver <mhw@netris.org>
To: Tobias Brandt <tob.brandt@googlemail.com>
Cc: 10918-done@debbugs.gnu.org
Subject: bug#10918: srfi-4 functions return wrong length for bytevectors
Date: Thu, 01 Mar 2012 16:20:28 -0500 [thread overview]
Message-ID: <87pqcw10ir.fsf@netris.org> (raw)
In-Reply-To: <CAOOWqioqEa9tjP9SEwUTrwcfMo9-a6-zn7_LdiJ5X7A6N1=ySw@mail.gmail.com> (Tobias Brandt's message of "Thu, 1 Mar 2012 15:56:54 +0100")
Tobias Brandt <tob.brandt@googlemail.com> writes:
> Applying any of the f/u/s*vector-length functions to
> a bytevector returns the wrong size. Specifically they
> multiply (instead of dividing) the size of the bytevector
> by the size of one element.
>
> scheme@(guile-user)> (use-modules (rnrs bytevectors))
> scheme@(guile-user)> (define bv (make-bytevector 4))
> scheme@(guile-user)> (bytevector-length bv)
> $1 = 4
> scheme@(guile-user)> (f32vector-length bv)
> $2 = 16
Fixed in ef405f8ba73fc57706d7155a2e008352416debcf.
Thanks for the bug report! :)
Mark
prev parent reply other threads:[~2012-03-01 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:56 bug#10918: srfi-4 functions return wrong length for bytevectors Tobias Brandt
2012-03-01 21:20 ` Mark H Weaver [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=87pqcw10ir.fsf@netris.org \
--to=mhw@netris.org \
--cc=10918-done@debbugs.gnu.org \
--cc=tob.brandt@googlemail.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).