ObjFW  Check-in [b84490ab4f]

Overview
Comment:Never block when the read buffer is non-empty

This was broken by 88f2f03. The problem only existed when something was
in the read buffer, but not processed completely, as after processing
the read buffer, it would go on to wait for data - but since not the
entire read buffer had been processed, it meant there was still data
left there that needed to be handled first.

Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | 0.8
Files: files | file ages | folders
SHA3-256: b84490ab4fcdac6125ac1c50e927ce7348207ac9885cb23c1d2233d2eab056ae
User & Date: js on 2016-03-20 12:05:46
Other Links: branch diff | manifest | tags
Context
2016-03-20
14:19
Use the locked queue for kqueue and epoll as well check-in: 85917ea0dd user: js tags: 0.8
12:05
Never block when the read buffer is non-empty check-in: b84490ab4f user: js tags: 0.8
10:55
undef __{unsafe_unretained,bridge,autoreleasing} check-in: ea5a19118a user: js tags: 0.8
Changes