public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> 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: Mon, 02 Dec 2002 16:36:00 -0000 [thread overview] Message-ID: <20021203003601.30502.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8778; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: bangerth@ticam.utexas.edu Cc: 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 02:28:07 +0100 Dear Wolfgang, I still don't agree with you ;-) On 2 Dec, Wolfgang Bangerth wrote: >> Initializing const arrays is usually supported by gcc. > > True, but not as static member variables. You can really compile the following with gcc!!! ------------------------snip here---------------------- template <int n> struct A { static const int i[] = { 1, 2 }; // works }; ------------------------snip here---------------------- Only with -pedantic you'll get a warning: test.cc:3: warning: ISO C++ forbids initialization of member constant `i' of non-integral type `const int[]' >> In fact, the code compiles if you just leave out the curly >> braces around the initializer. That refers to the original testcase. Just try it! Best regards, Volker
next reply other threads:[~2002-12-03 0:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-02 16:36 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-03 7:56 Wolfgang Bangerth 2002-12-03 7:26 Gabriel Dos Reis 2002-12-03 6:56 Wolfgang Bangerth 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=20021203003601.30502.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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: linkBe 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).