public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11393] Initializer of static const float class member is not legal in c++98
Date: Mon, 07 Jul 2003 23:23:00 -0000 [thread overview]
Message-ID: <20030707232335.6317.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030701172459.11393.rearnsha@gcc.gnu.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11393
------- Additional Comments From bangerth at dealii dot org 2003-07-07 23:23 -------
I certainly concur. The interaction of the flags -std, -ansi, -pedantic is
not at all clear to me, and it would be good if either their relative
meaning if one of the other flags is given, is explained in detail, or
if they are meant to represent orthogonal concepts. One of the questions
here is: does -std=XX define a minimal or a maximal set of things gcc
has to support, as viewed in the presence of gcc extensions?
W.
next prev parent reply other threads:[~2003-07-07 23:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 17:25 [Bug c++/11393] New: " rearnsha at gcc dot gnu dot org
2003-07-01 17:31 ` [Bug c++/11393] " pinskia at physics dot uc dot edu
2003-07-02 16:43 ` rearnsha at gcc dot gnu dot org
2003-07-02 16:47 ` pinskia at physics dot uc dot edu
2003-07-02 17:06 ` rearnsha at arm dot com
2003-07-02 23:28 ` jsm28 at cam dot ac dot uk
2003-07-04 11:10 ` gdr at integrable-solutions dot net
2003-07-04 11:10 ` [Bug c++/11393] New: " Gabriel Dos Reis
2003-07-04 11:33 ` [Bug c++/11393] " gdr at integrable-solutions dot net
2003-07-04 11:33 ` gdr at integrable-solutions dot net
2003-07-04 11:35 ` gdr at integrable-solutions dot net
2003-07-07 10:25 ` rearnsha at gcc dot gnu dot org
2003-07-07 10:25 ` rearnsha at gcc dot gnu dot org
2003-07-07 23:23 ` bangerth at dealii dot org [this message]
2003-08-11 15:32 ` lerdsuwa at gcc dot gnu dot org
2003-08-23 0:39 ` dhazeghi at yahoo dot com
2004-11-09 23:09 ` pinskia at gcc dot gnu dot org
2005-04-18 17:32 ` pinskia at gcc dot gnu dot org
2005-04-18 17:38 ` pinskia at gcc dot gnu dot org
2005-05-10 17:44 ` pinskia at gcc dot gnu dot org
[not found] <bug-11393-374@http.gcc.gnu.org/bugzilla/>
2007-12-02 22:11 ` pinskia at gcc dot gnu dot org
[not found] <bug-11393-4@http.gcc.gnu.org/bugzilla/>
2012-10-25 22:41 ` paolo.carlini at oracle dot com
2012-10-25 23:30 ` manu at gcc dot gnu.org
2012-10-25 23:44 ` manu at gcc dot gnu.org
2012-10-25 23:49 ` rnewman at compubrite dot com
2012-10-26 0:02 ` redi at gcc dot gnu.org
2012-10-26 0:16 ` manu at gcc dot gnu.org
2012-10-26 0:24 ` manu at gcc dot gnu.org
2012-10-26 1:12 ` redi at gcc dot gnu.org
2012-10-26 1:54 ` manu at gcc dot gnu.org
2012-10-26 2:05 ` manu at gcc dot gnu.org
2012-10-26 2:13 ` redi at gcc dot gnu.org
2012-10-26 11:44 ` paolo.carlini at oracle dot com
2012-10-26 11:45 ` manu at gcc dot gnu.org
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=20030707232335.6317.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).