Thien-Thi Nguyen t...@gnu.org 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
Thien-Thi Nguyen t...@gnuvola.org 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
Hi Ian,
Ian Price ianpric...@googlemail.com writes:
Thien-Thi Nguyen t...@gnu.org 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
Mark H Weaver m...@netris.org 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.
Proc ‘uniform-vector-read!’ is deprecated (ugh), and its implementation
rebased onto ‘(rnrs io ports) get-bytevector-n!’. Unfortunately, there
seems to be a glitch in the arg shuffling. Here is /tmp/foo.scm:
foo.scm
Description: application/scheme
and here is a series of invocations that
