Hi,
Kevin Ryde <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Ludovic Courtès) writes:
>>
>> Right. That's an incompatible change if the _output_ is buffered.
>> Input can be buffered, though, without this being visible by users.
>
> Alas, that too is in an incompatible change, because recv! i
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> Below is a tentative patch (I chose more meaningful names since they
> don't relate to `setvbuf(3)').
Call them setvbuf. Two names for the same thing is more confusing
than one (slightly obscure) name.
> Besides, how about applying the change I ori
[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 probl
Kevin Ryde <[EMAIL PROTECTED]> writes:
> Neil Jerram <[EMAIL PROTECTED]> writes:
>>
>> "tail array not allowed if struct has a zero length layout"
>
> You don't think "unless ends in R,W,O" is enough to exclude an empty
> layout? The aim, slightly, is to hint at the solution within the
> error me
