[EMAIL PROTECTED] (Ludovic Courtès) writes: > > (uniform-vector-read! vec port)))
Slackness in the implementation of that function. It knows a size to read and should come out as a read() system call of that size. Yet it always goes through the port buffer. You need to post the problem instead of leaping to a "solution". read-string!/partial is much better in that respect. Maybe that func should be loosened up to work on non-fports too, that could be nice. It's a bit of a failing of the ptab port functions that there's no "read N bytes", but that needn't prevent uniform-vector-read! doing the right thing on fports. Could think about whether it ought to make multiple calls to fill the requested size. I guess that's how it is now, in effect, so probably yes. Could also think if those calls should then cope with O_NONBLOCK too, by sleeping in select() if finding there's nothing to read yet. On a single read call I would say let it throw an error, but if the aim is to block until the requested size then it's easy enough to cope. _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
