Again, if a (blocking) socket has received some data before the timeout, but not enough to satisfy the number specified on the sysread, can_read() will have returned true, but will sysread block or not?I'd have thought that it's obvious that sysread blocks if there's no data, but otherwise returns the number of bytes actually read.
Those Win32 issues sound nasty. I have three questions:
-David
In reply to Re^7: How to make sysread timeout
by erroneousBollock
in thread How to make sysread timeout
by redss
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |