public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/2831 Date: Tue, 22 May 2001 07:46:00 -0000 [thread overview] Message-ID: <20010522144600.6512.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/2831; it has been noted by GNATS. From: lerdsuwa@gcc.gnu.org To: at@sourceware.cygnus.com, fspam@sourceware.cygnus.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/2831 Date: 22 May 2001 14:38:58 -0000 Synopsis: operator ?: requires storage for initialized static member constants State-Changed-From-To: open->closed State-Changed-By: lerdsuwa State-Changed-When: Tue May 22 07:38:58 2001 State-Changed-Why: Not a bug. The definition of static data member is required in both situations, flags and aflags assignments. However, a standard-compliant does not have to verify this (as can be seen from the aflag assignment) to allow optimization. See section 9.4.2 para 4-5 of the standard: 4 If a static data member is of const integral or const enumeration type, its declaration in the class definition can specify a constant-initializer which shall be an integral constant expression (5.19). In that case, the member can appear in integral constant expressions within its scope. The member shall still be defined in a namespace scope if it is used in the program and the namespace scope definition shall not contain an initializer. 5 There shall be exactly one definition of a static data member that is used in a program; no diagnostic is required; see 3.2. ... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2831&database=gcc
reply other threads:[~2001-05-22 7:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010522144600.6512.qmail@sourceware.cygnus.com \ --to=lerdsuwa@gcc.gnu.org \ --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).