array vs. bytevector

array vs. bytevector

[Johan Hidding]

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

Re: array vs. bytevector

[Ludovic Courtès]

Hi,

Johan Hidding <johannes.hidding@gmail.com> skribis:

> It would be simplest if (put-bytevector ...) would
> accept an array as argument, but this gives a type-error

It actually works with SRFI-4 vectors (info "(guile) SRFI-4 and
Bytevectors"):

  scheme@(guile-user)> (use-modules(rnrs io ports))
  scheme@(guile-user)> (put-bytevector (%make-void-port "w") #u8(1 2 3))

Does it help?

Ludo’.

Re: array vs. bytevector

[Johan Hidding]

Hi,
I think I found the answer in that I should use (array-contents ...) as such:
(import (rnrs io ports))
(put-bytevector (%make-void-port "w") (array-contents #2f64((1 2) (3 4))))
Cheers, Johan


2011/9/15 Ludovic Courtès <ludo@gnu.org>:
> Hi,
>
> Johan Hidding <johannes.hidding@gmail.com> skribis:
>
>> It would be simplest if (put-bytevector ...) would
>> accept an array as argument, but this gives a type-error
>
> It actually works with SRFI-4 vectors (info "(guile) SRFI-4 and
> Bytevectors"):
>
>  scheme@(guile-user)> (use-modules(rnrs io ports))
>  scheme@(guile-user)> (put-bytevector (%make-void-port "w") #u8(1 2 3))
>
> Does it help?
>
> Ludo’.
>
>
>