public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8778: ICE on illegal initialization of non-integral static in-class constant
Date: Tue, 03 Dec 2002 07:56:00 -0000	[thread overview]
Message-ID: <20021203155608.29575.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8778; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Volker Reichelt <reichelt@igpm.rwth-aachen.de>, <gcc-gnats@gcc.gnu.org>,
   <gcc-bugs@gcc.gnu.org>, <sgunderson@bigfoot.com>
Subject: Re: c++/8778: ICE on illegal initialization of non-integral static
 in-class constant
Date: Tue, 3 Dec 2002 09:47:50 -0600 (CST)

 Gaby, Volker,
 
 let's settle this matter:
 
 
 > | > ------------------------snip here----------------------
 > | > template <int n> struct A
 > | > {
 > | >     static const int i[] = { 1, 2 };       // works
 > | > };
 > 
 > If this compiles with GCC then that is a compiler bug.  The program
 > construct is invalid.
 > 
 > [...]
 > 
 > | So maybe we can meet in the middle: "The code is illegal based on the C++ 
 > | standard, but is accepted as a gcc extension"?
 > 
 > I doubt that is an extension.
 
 I just filed report PR 8797 stating that the above syntax should not be
 accepted, or alternatively that the "extension" should be documented in
 the manual. I guess I lean towards the first alternative. Note also that
 using -pedantic yields a _warning_, not an error on the code above, so I
 guess having a separate report is justified.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-12-03 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03  7:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-03  7:26 Gabriel Dos Reis
2002-12-03  6:56 Wolfgang Bangerth
2002-12-02 16:36 Volker Reichelt
2002-12-02 16:26 Wolfgang Bangerth
2002-12-02 16:06 Volker Reichelt
2002-12-02 12:49 bangerth

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=20021203155608.29575.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).