Re: portability of fopen and 'e' (O_CLOEXEC) flag

[Bruno Haible]

Tim Rühsen wrote on 2020-05-12:
> > How about using open() with O_CLOEXEC, and then fdopen()?
> 
> Thanks. Sure, this is possible. Doing so at dozens of places (or more)
> asks for an implementation in gnulib :)

Additionally, gnulib is the right place to do this because - as Eric said -
the 'e' flag is already scheduled for being added to the next POSIX version:
https://www.austingroupbugs.net/view.php?id=411

My evaluation of current platform support was incorrect: Current versions of
FreeBSD, NetBSD, OpenBSD, Solaris, Cygwin, and even Minix already support it.


2020-05-24  Bruno Haible  <address@hidden>

        fopen-gnu: Add tests.
        * tests/test-fopen-gnu.c: New file.
        * modules/fopen-gnu-tests: New file.

        fopen-gnu: New module.
        Suggested by Tim Rühsen <address@hidden> in
        <https://lists.gnu.org/archive/html/bug-gnulib/2020-05/msg00119.html>.
        * lib/fopen.c (rpl_fopen): When the fopen-gnu module is enabled and the
        mode contains an 'x' or 'e' flag, use open() followed by fdopen().
        * m4/fopen.m4 (gl_FUNC_FOPEN_GNU): New macro.
        * modules/fopen-gnu: New file.
        * doc/posix-functions/fopen.texi: Document the 'fopen-gnu' module.

0001-fopen-gnu-New-module.patch
Description: Text Data

0002-fopen-gnu-Add-tests.patch
Description: Text Data