GME
13
|
write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.
no platform currently tests the pipes health.
write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.
no platform currently tests the pipes health.
write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.
no platform currently tests the pipes health.
Some platforms cannot toggle between blocking and nonblocking, and when passing a pipe as a standard handle to an application which does not expect it, a non-blocking stream will fluxor the client app.
With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.
With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.
With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.
*end breaks type safety; where *buf is const, *end needs to be declared as const in APR 2.0
Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.
Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.
Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.
Passing proc as a *proc rather than **proc was an odd choice for some platforms... this should be revisited in 1.0