Problem with u8vector ports?
Hi, I think I've just uncovered a bug with u8vector ports when the u8vector is more than 64 elements long. Here is the simplest way to reproduce this problem:
(define v (make-u8vector 64 32)) (u8vector-set! v 62 65) (with-input-from-u8vector v read) A (define v (make-u8vector 65 32)) (u8vector-set! v 63 65) (with-input-from-u8vector v read) (u8vector-rbuf-fill #<input-port #11 (u8vector)> 1 #t) 1>
The last two lines are produced by lines 3264-3265 of _io.scm, if this can be of any help. Dominique
Afficher les réponses par date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31-Jan-07, at 9:16 PM, <schemeway@sympatico.ca> <schemeway@sympatico.ca> wrote:
I think I've just uncovered a bug with u8vector ports when the u8vector is more than 64 elements long. Here is the simplest way to reproduce this problem:
(define v (make-u8vector 64 32)) (u8vector-set! v 62 65) (with-input-from-u8vector v read) A (define v (make-u8vector 65 32)) (u8vector-set! v 63 65) (with-input-from-u8vector v read) (u8vector-rbuf-fill #<input-port #11 (u8vector)> 1 #t) 1>
The last two lines are produced by lines 3264-3265 of _io.scm, if this can be of any help.
This is a long standing bug with the buffering. It's on my TODO... Marc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFF0hIn//V9Zc2T/v4RAsj1AJ43+XgxOB1Ct0HXibfNIp32DrmfNACeJ04Z prWadizIc/B96c8SDy7E/Po= =0Qw6 -----END PGP SIGNATURE-----
participants (2)
-
Marc Feeley -
schemeway@sympatico.ca