Nikita Popov d59aac58b3 Report errors from stream read and write operations ... The php_stream_read() and php_stream_write() functions now return an ssize_t value, with negative results indicating failure. Functions like fread() and fwrite() will return false in that case. As a special case, EWOULDBLOCK and EAGAIN on non-blocking streams should not be regarded as error conditions, and be reported as successful zero-length reads/writes instead. The handling of EINTR remains unclear and is internally inconsistent (e.g. some code-paths will automatically retry on EINTR, while some won't). I'm landing this now to make sure the stream wrapper ops API changes make it into 7.4 -- however, if the user-facing changes turn out to be problematic we have the option of clamping negative returns to zero in php_stream_read() and php_stream_write() to restore the old behavior in a relatively non-intrusive manner.		2019-07-22 17:17:28 +02:00
..
tests	Report errors from stream read and write operations	2019-07-22 17:17:28 +02:00
bug71263.phpt	Report errors from stream read and write operations	2019-07-22 17:17:28 +02:00
bz2_filter.c	Remove local variables	2019-02-03 21:03:00 +01:00
bz2.c	Report errors from stream read and write operations	2019-07-22 17:17:28 +02:00
config.m4	Normalize comments in *nix build system m4 files	2019-05-12 18:43:03 +02:00
config.w32	Remove unused Git attributes ident	2018-07-25 00:53:25 +02:00
CREDITS
php_bz2.h	Remove local variables	2019-02-03 21:03:00 +01:00