public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10112: static data member is not correctly initialized
Date: Tue, 18 Mar 2003 01:56:00 -0000	[thread overview]
Message-ID: <20030318015601.24672.qmail@sources.redhat.com> (raw)

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

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Giovanni Bajo" <giovannibajo@libero.it>
Cc: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>, <gcc-gnats@gcc.gnu.org>,
   <gcc-bugs@gcc.gnu.org>, <o.kullmann@swansea.ac.uk>, <nathan@gcc.gnu.org>
Subject: Re: c++/10112: static data member is not correctly initialized
Date: 18 Mar 2003 02:46:40 +0100

 "Giovanni Bajo" <giovannibajo@libero.it> writes:
 
 [...]
 
 | Nathan, I agree that the order of instantiation is implementation defined,
 | but the initialization of the static data members should happen before any
 | template is instantiated.
 
 From which parts of the standard did read that?
 
 | =A714.7.1p8 decouples initialization of static data
 | members and instantiation of class templates, saying that <<implicit
 | instantiation of a class template does not cause any static data members =
 of
 | that class to be implicitly instantiated>>. In fact, <<static data members
 | are initialized [...] exactly like nonlocal objects>> (=A79.4.2p7), <<bef=
 ore
 | any other initialization takes place>> (=A73.6.2p1) (and of course only if
 | <<the static data member is itself used in a way that requires the
 | definition of the static data member to exist>> (=A714.7.1p1).
 
 I can't read that to imply the your first assertion quoted above.
 
 -- Gaby


             reply	other threads:[~2003-03-18  1:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  1:56 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-18  2:46 Gabriel Dos Reis
2003-03-18  2:06 Giovanni Bajo
2003-03-18  1:46 Giovanni Bajo
2003-03-18  0:16 Wolfgang 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=20030318015601.24672.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --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).