> Dirk, no matter where you add the code, it is completely not portable, and
> the result is actually undefined. Some platforms zero out the timeout,
> others don't. Some leave the timeout alone, others subtract the elapsed
> time. Unless you include a bunch of autoconf macros to determine whic
On Sun, 1 Apr 2001, Dirk-Willem van Gulik wrote:
>
> On Sun, 1 Apr 2001 [EMAIL PROTECTED] wrote:
>
> > There is no suitable function, and writing one is not possible. Many
> > platforms zero out the timeout, so that we can't cleanly recalculate
> > the new timeout.
> >
> No trouble - I'll add it
On Sun, 1 Apr 2001 [EMAIL PROTECTED] wrote:
> There is no suitable function, and writing one is not possible. Many
> platforms zero out the timeout, so that we can't cleanly recalculate
> the new timeout.
>
No trouble - I'll add it to 'ab' then as a small inernal _send().
Dw
On Sun, 1 Apr 2001, Dirk-Willem van Gulik wrote:
>
> Am I right to understand that it is the designed intention of apr_send()
> to do a best efford write to the network; it retries' on EINTR and under
> certain conditions on EAGAIN/EWOULDBLOCK - but basically returns as soon
> as something is writ
