From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28779 invoked by alias); 7 Nov 2002 11:16:05 -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 28759 invoked by uid 71); 7 Nov 2002 11:16:05 -0000 Date: Thu, 07 Nov 2002 03:16:00 -0000 Message-ID: <20021107111605.28757.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andreas Schwab Subject: Re: preprocessor/8449: Ellipsis in 3...5 not recognized properly Reply-To: Andreas Schwab X-SW-Source: 2002-11/txt/msg00362.txt.bz2 List-Id: The following reply was made to PR preprocessor/8449; it has been noted by GNATS. From: Andreas Schwab To: "Christian Ehrhardt" Cc: Neil Booth , gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: preprocessor/8449: Ellipsis in 3...5 not recognized properly Date: Thu, 07 Nov 2002 12:09:54 +0100 "Christian Ehrhardt" writes: |> int a[2] = {[0...1] = 1}; This is a constraint violation. 0...1 is a preprocessing token (a pp-number, 6.4.8), but not a token, thus it violates 6.4[#2]: "Each preprocessing token that is converted to a token shall have the lexical form of a keyword, an identifier, a constant, a string literal, or a punctuator." Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."