From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11601 invoked by alias); 6 May 2003 01:50:10 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 11582 invoked by uid 48); 6 May 2003 01:50:10 -0000 Date: Tue, 06 May 2003 01:50:00 -0000 Message-ID: <20030506015010.11581.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gonz@ratloop.com, nobody@gcc.gnu.org From: giovannibajo@libero.it Reply-To: giovannibajo@libero.it, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gonz@ratloop.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10634: in-class initialization of static data members no longer allowed X-SW-Source: 2003-05/txt/msg00335.txt.bz2 List-Id: Synopsis: in-class initialization of static data members no longer allowed State-Changed-From-To: open->closed State-Changed-By: bajo State-Changed-When: Tue May 6 01:50:09 2003 State-Changed-Why: Not a bug. GCC does the right thing now: ยง9.4.2 specifies that only static data member of const integral or const enumeration type can be initialized at declaration time. "unsigned char* const" is not a const integral type. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10634