unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: dfsr@riseup.net (Diogo F. S. Ramos)
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: guile-devel@gnu.org
Subject: Re: `bytevector-length' doesn't accept a shared array from a bytevector
Date: Tue, 21 Feb 2017 15:51:11 -0300	[thread overview]
Message-ID: <87a89f5qe8.fsf@riseup.net> (raw)
In-Reply-To: <877B3F28-97FF-4B82-86BD-F6860C768131@bluewin.ch> (Daniel Llorens's message of "Tue, 21 Feb 2017 15:18:08 +0100")

> On 21 Feb 2017, at 14:21, Diogo F. S. Ramos <dfsr@riseup.net> wrote:
>
>> I want to take the length of a shared array, but `bytevector-length'
>> throws an error claiming the shared array isn't a bytevector, even
>> though it prints the error argument as one.
>> 
>> I am using Guile 2.0.11, Debian Stable package 2.0.11+1-9.
>
> This is addressed in 2.1, by
> eb3d623da57e6d31a58d95f932345fb761f9b701. Your example will print
> #1vu8(0 0 ...) to signify that it's not a bytevector. You can use
> array-length here.

Thank you.

I didn't realize shared arrays are not bytevectors anymore and wrongly
assumed bytevector procedures could be applied to arrays, even tho array
procedures can be applied to bytevectors.



  reply	other threads:[~2017-02-21 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 13:21 `bytevector-length' doesn't accept a shared array from a bytevector Diogo F. S. Ramos
2017-02-21 14:18 ` Daniel Llorens
2017-02-21 18:51   ` Diogo F. S. Ramos [this message]
2017-02-21 20:07     ` Daniel Llorens

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=87a89f5qe8.fsf@riseup.net \
    --to=dfsr@riseup.net \
    --cc=daniel.llorens@bluewin.ch \
    --cc=guile-devel@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).