public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/8449: Ellipsis in 3...5 not recognized properly Date: Thu, 07 Nov 2002 03:16:00 -0000 [thread overview] Message-ID: <20021107111605.28757.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1005 bytes --] The following reply was made to PR preprocessor/8449; it has been noted by GNATS. From: Andreas Schwab <schwab@suse.de> To: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> Cc: Neil Booth <neil@daikokuya.co.uk>, 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" <ehrhardt@mathematik.uni-ulm.de> 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."
next reply other threads:[~2002-11-07 11:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-07 3:16 Andreas Schwab [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-07 3:38 neil 2002-11-07 1:26 Christian Ehrhardt 2002-11-07 0:26 Neil Booth 2002-11-04 8:56 Christian Ehrhardt 2002-11-04 8:26 ehrhardt
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=20021107111605.28757.qmail@sources.redhat.com \ --to=schwab@suse.de \ --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: linkBe 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).