From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25404 invoked by alias); 21 Aug 2003 15:45:06 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 25395 invoked by alias); 21 Aug 2003 15:45:05 -0000 Date: Thu, 21 Aug 2003 15:45:00 -0000 Message-ID: <20030821154505.25392.qmail@sources.redhat.com> From: "Castalia at idaeim dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20030821041204.12003.Castalia@idaeim.com> References: <20030821041204.12003.Castalia@idaeim.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/12003] FILE* variable initialized to stderr (not constant error) X-Bugzilla-Reason: CC X-SW-Source: 2003-08/txt/msg02326.txt.bz2 List-Id: PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12003 ------- Additional Comments From Castalia at idaeim dot com 2003-08-21 15:45 ------- Subject: Re: FILE* variable initialized to stderr (not constant error) Thanks for the prompt reply. You've confirmed my suspicions. This does create a really awkward situation for C code that expects to initialize error/warning reporting FILE* variables to stderr by default. Any suggestions for a workaround? Thnx, Bradford Castalia Senior Systems Analyst Planetary Image Research Laboratory University of Arizona jsm at polyomino dot org dot uk wrote: > > PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12003 > > ------- Additional Comments From jsm at polyomino dot org dot uk 2003-08-21 12:46 ------- > Subject: Re: FILE* variable initialized to stderr (not constant > error) > > On Thu, 21 Aug 2003, pinskia at gcc dot gnu dot org wrote: > > > Note stderr is defined by the libc, not by GCC so that is why it worked > > in Solaris and not in FreeBSD but also the c standard allows > > stderr/stdout/stdin to be non-constant values so this is a non-bug. > > It is also explicitly listed as a non-bug in the bug reporting > instructions, under "Cannot initialize a static variable with stdin.". > Perhaps mentioning stdout and stderr there as well would make bug > submitters more likely to see that this non-bug is what they're > encountering? (And indicating that FreeBSD now has this property as well, > not just GNU libc.) > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter.