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/9469: [3.2/3.3/3.4 regression] initializer element is (allegedly) not constant
Date: Tue, 28 Jan 2003 16:06:00 -0000	[thread overview]
Message-ID: <20030128160600.15525.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: akpm@digeo.com, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/9469: [3.2/3.3/3.4 regression] initializer element is (allegedly)
 not constant
Date: Tue, 28 Jan 2003 10:04:53 -0600 (CST)

 On Tue, 28 Jan 2003, Joseph S. Myers wrote:
 
 > On 27 Jan 2003 bangerth@dealii.org wrote:
 > 
 > >     Confirmed. This used to compile until 3.0, but fails with
 > >     3.2, 3.3, 3.4. I must admit that I don't know exactly
 > >     whether this is legal code, but it looks like, and in this
 > >     case it is a regression
 > 
 > It has never been valid C to use an expression of aggregate type as part
 > of an initializer, only as a the whole initializer, though the broken old
 > implementation of compound literals may have allowed this.  I'll leave it
 > up to Jakub to decide whether it makes any sense to allow this as another
 > compatibility case of compound literals in gnu89 mode.
 
 Thanks for clarifying this. Did you notify Jakub of this report? He's not 
 on the CC:-list.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-01-28 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 16:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28 18:26 Wolfgang Bangerth
2003-01-28 18:06 Joseph S. Myers
2003-01-28  7:46 Joseph S. Myers
2003-01-27 23:52 bangerth

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