[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout

From: Akim Demaille
Subject: Re: [PATCH] do not ignore errors like ENOSPC, EIO when writing to stdout
Date: Tue, 31 Jan 2012 09:46:43 +0100

Le 29 janv. 2012 à 19:22, Jim Meyering a écrit :

> From: Jim Meyering <address@hidden>
> Date: Sun, 29 Jan 2012 12:50:32 +0100
> Subject: [PATCH] do not ignore errors like ENOSPC,EIO when writing to stdout
> Standard output was never explicitly closed, so we could not
> detect failure.  Thus, bison would ignore the errors of writing
> to a full file system and getting an I/O error on write, but only
> for standard output, e.g., for --print-localedir, --print-datadir,
> --help and some verbose output.
> Now, "bison --print-datadir > /dev/full" reports the write failure:
> bison: write error: No space left on device
> Before, it would exit 0 with no diagnostic, implying success.
> This is not an issue for "--output=-" or the other FILE-accepting
> command-line options, because unlike most other GNU programs,
> an output file argument of "-" is treated as the literal "./-",
> rather than standard output.
> * bootstrap.conf (gnulib_modules): Add closeout.
> * src/main.c: Include "closeout.h".
> Use atexit to ensure we close stdout.
> * .gitignore: Ignore new files pulled in via gnulib-tool.

Installed in branch-2.5.

Is there some standard in the gnulib universe on the names to
give to the various branches?  In Bison, master is the next major
release, and we use branch-X.Y for the maintenance branches, but
some version independent naming scheme would be fine.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]