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++/10112: static data member is not correctly initialized
Date: Tue, 18 Mar 2003 00:16:00 -0000	[thread overview]
Message-ID: <20030318001601.5509.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: giovannibajo@libero.it, <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
   <o.kullmann@swansea.ac.uk>, <nathan@gcc.gnu.org>
Cc:  
Subject: Re: c++/10112: static data member is not correctly initialized
Date: Mon, 17 Mar 2003 18:15:06 -0600 (CST)

 I think with this code, A::p1 is statically initialized (being a POD 
 type), while B::a is dynamically initialized (having a user-defined 
 constructor). I think I remember that the standard specifies that static 
 initializers always run before dynamic ones, irrespective of the order in 
 which they appear in the source file. In that case, this would not be a 
 bug.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-18  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  0:16 Wolfgang Bangerth [this message]
2003-03-18  1:46 Giovanni Bajo
2003-03-18  1:56 Gabriel Dos Reis
2003-03-18  2:06 Giovanni Bajo
2003-03-18  2:46 Gabriel Dos Reis

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=20030318001601.5509.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).