Eric Blake wrote:
> Also, should we offer O_BINARY/O_TEXT support on
> cygwin, using setmode()? (On Linux, O_BINARY and O_TEXT are both 0, so we
> have implicitly already done so).
After 1 sec of thinking, yes. There is no reason to offer O_BINARY, O_TEXT in
accept4 but not in pipe2. Committed:
Eric Blake asked:
> > /* Check the supported flags. */
> > if ((flags & ~(O_CLOEXEC | O_BINARY | O_TEXT)) != 0)
>
> Is there any way to support NONBLOCK in Woe32?
Not really. The concept of asynchronous I/O in Woe32 means that the I/O
processes independently, and the caller is notified at th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 8/22/2009 10:46 AM:
> /* Native Woe32 API. */
>
> # include
>
> int
> pipe2 (int fd[2], int flags)
> {
> /* Check the supported flags. */
> if ((flags & ~(O_CLOEXEC | O_BINARY | O_TEXT)) != 0)
Is there any way to
> already possible to implement pipe2.
For reference, the introduction of pipe2 in Linux was here:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=ed8cae8ba01348bfd8f4648dd807b04d7f08
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=
Bruno Haible
New module 'pipe2'.
* lib/unistd.in.h (pipe2): New declaration.
* lib/pipe2.c: New file.
* m4/pipe2.m4: New file.
* m4/unistd_h.m4 (gl_UNISTD_H_DEFAULTS): Initialize GNULIB_PIPE2 and
HAVE_PIPE2.
* modules/unis
