public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Castalia at idaeim dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12003] FILE* variable initialized to stderr (not constant error)
Date: Thu, 21 Aug 2003 15:45:00 -0000 [thread overview]
Message-ID: <20030821154505.25392.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030821041204.12003.Castalia@idaeim.com>
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.
prev parent reply other threads:[~2003-08-21 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 4:12 [Bug c/12003] New: " Castalia at idaeim dot com
2003-08-21 11:50 ` [Bug c/12003] " pinskia at gcc dot gnu dot org
2003-08-21 12:46 ` jsm at polyomino dot org dot uk
2003-08-21 15:45 ` Castalia at idaeim dot com [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030821154505.25392.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).