This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: stderr vs. STDERR_FILENO

From: Andreas Schwab <schwab at suse dot de>
To: "Zack Weinberg" <zack at codesourcery dot com>
Cc: Mark Mitchell <mark at codesourcery dot com>, bkoz at redhat dot com,gcc-patches at gcc dot gnu dot org, phil at codesourcery dot com
Date: Wed, 25 Feb 2004 02:54:59 +0100
Subject: Re: stderr vs. STDERR_FILENO
References: <403B784E.6070508@codesourcery.com> <jen078xwvc.fsf@sykes.suse.de><403BB934.7040604@codesourcery.com> <jeu11gf4cm.fsf@sykes.suse.de><403BE162.9040202@codesourcery.com> <jellmsf27b.fsf@sykes.suse.de><403BEB12.7000107@codesourcery.com><87u11gynh1.fsf@egil.codesourcery.com>

"Zack Weinberg" <zack@codesourcery.com> writes:

> I note that glibc does not do this, and there is wording in C99 which
> could be read to disallow it (7.19.5.4p4 - "[freopen] first attempts
> to close any file that is associated with the specified stream") so
> Mark's concern is valid.

POSIX is even more explicit about that.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- stderr vs. STDERR_FILENO
  - From: Mark Mitchell
- Re: stderr vs. STDERR_FILENO
  - From: Andreas Schwab
- Re: stderr vs. STDERR_FILENO
  - From: Mark Mitchell
- Re: stderr vs. STDERR_FILENO
  - From: Andreas Schwab
- Re: stderr vs. STDERR_FILENO
  - From: Mark Mitchell
- Re: stderr vs. STDERR_FILENO
  - From: Andreas Schwab
- Re: stderr vs. STDERR_FILENO
  - From: Mark Mitchell
- Re: stderr vs. STDERR_FILENO
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]