Thien-Thi Nguyen writes:
> ERROR: In procedure uniform-vector-read!:
> ERROR: In procedure get-bytevector-n!: Value out of range: 4
>
> FWIW, Guile 1.8.8 produces same output as ‘ok’ on a similar (sans the
> ‘use-modules’ and ‘uniform-vector-element-size’ noise) input, so i think
> this situation
Thien-Thi Nguyen writes:
> I think it is good to fix it regardless of the remaining time. Leaving
> it in a known-bad state sends a message tinged w/ coercion -- Not Cool.
There has been talk of making the next version the first release of the
next major version. If the next version was the maj
Hi Ian,
Ian Price writes:
> Thien-Thi Nguyen writes:
>
>> ERROR: In procedure uniform-vector-read!:
>> ERROR: In procedure get-bytevector-n!: Value out of range: 4
>>
>> FWIW, Guile 1.8.8 produces same output as ‘ok’ on a similar (sans the
>> ‘use-modules’ and ‘uniform-vector-element-size’ nois
Mark H Weaver writes:
> It will certainly not be removed in the 2.0.x release series, which will
> remain in use for at least another year or so. Therefore, this should
> definitely be fixed. Would you like to do it?
As long as it wasn't _next_ release, I am happy to fix it.
Patch pushed. Clo
Hello,
guile-2.0 (2.0.9) does not work on ia64. It builds, but the executable
segfaults:
SNARF regex-posix.doc
GEN guile-procedures.texi
/bin/bash: line 1: 30416 Broken pipe cat alist.doc arbiters.doc
array-handle.doc array-map.doc arrays.doc async.doc
writes:
> The first error emerges at line 1802 in install.output, which reads:
> ERROR: bit-operations.test: bit-extract: documented? - arguments: (
> (keyword-argument-error # (file #:key binary encoding guess-encoding)> "Invalid keyword" () #f))
This one is very peculiar, you would have thoug
