From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-31463-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24688 invoked by alias); 18 Mar 2003 01:56:02 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 24673 invoked by uid 71); 18 Mar 2003 01:56:01 -0000
Date: Tue, 18 Mar 2003 01:56:00 -0000
Message-ID: <20030318015601.24672.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
Subject: Re: c++/10112: static data member is not correctly initialized
Reply-To: Gabriel Dos Reis <gdr@integrable-solutions.net>
X-SW-Source: 2003-03/txt/msg01193.txt.bz2
List-Id: <gcc-prs.sourceware.org>

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