From: Johan Hidding <johannes.hidding@gmail.com>
To: guile-user@gnu.org
Subject: array vs. bytevector
Date: Thu, 15 Sep 2011 16:45:57 +0200 [thread overview]
Message-ID: <CAEz5FLbJ8+M1HuRd+qPd5bfG7WREySC6_FBdfxPevd6Av90DGg@mail.gmail.com> (raw)
Hi,
I was playing around with guile arrays, saving and restoring them from
disk. There are nice method called
(uniform-array-read! ...) and (uniform-array-write ...), however these
are depricated in favour of bytevector i/o. What is the prefered
method to interpret the data as an array? There is
(bytevector-ieee-double-ref ...) but that is quite cumbersome
especially when dealing with multidimensional complex arrays; then I
could use (c64vector-ref ...), but this interface is not as versatile
as with arrays. It would be simplest if (put-bytevector ...) would
accept an array as argument, but this gives a type-error (at least in
guile-2.0.2)
Any help would be greatly appreciated.
Cheers, Johan
next reply other threads:[~2011-09-15 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 14:45 Johan Hidding [this message]
2011-09-15 15:08 ` array vs. bytevector Ludovic Courtès
2011-09-15 16:19 ` Johan Hidding
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=CAEz5FLbJ8+M1HuRd+qPd5bfG7WREySC6_FBdfxPevd6Av90DGg@mail.gmail.com \
--to=johannes.hidding@gmail.com \
--cc=guile-user@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).