On Fri 12 Aug 2011 05:44, ri...@happyleptic.org writes:
> Between stable-2.0 and master a patch changed the C representation
> of the SCM type so that it is now a union.
As a result of this constant-expression issue, I have reverted those
patches. Now `master' uses the same SCM representation as
That's exactly what I was thinking, Kernel that is. But, I didn't
wanna sound like an idiot saying, "if only we had FExprs"...
On Thu, Sep 15, 2011 at 2:11 PM, Andy Wingo wrote:
> On Tue 13 Sep 2011 12:09, "Bill Schottstaedt"
> writes:
>
>> if lambda were applicable, this would work in both cas
On Tue 13 Sep 2011 12:09, "Bill Schottstaedt" writes:
> if lambda were applicable, this would work in both cases:
>
> (define-macro (progv vars vals . body)
> `(apply (apply lambda ,vars ',body) ,vals))
That's fun! Makes me think of Kernel. I think you'd enjoy Kernel,
Bill, if you haven't se
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 :
> Hi,
>
> Johan Hidding skribis:
>
>> It would be simplest if (put-bytev
Hi,
Johan Hidding 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)> (
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
(b
