public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8290: [3.2/3.3 regression] Initialization with compound literals during declaration fails with gcc 3.2
Date: Mon, 02 Dec 2002 16:46:00 -0000	[thread overview]
Message-ID: <20021203004602.1491.qmail@sources.redhat.com> (raw)

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

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <bangerth@dealii.org>,  <gcc-bugs@gcc.gnu.org>,  <kipp@sgl.crestech.ca>, 
     <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c/8290: [3.2/3.3 regression] Initialization with compound literals
 during declaration fails with gcc 3.2
Date: Tue, 3 Dec 2002 00:38:46 +0000 (GMT)

 On 2 Dec 2002 bangerth@dealii.org wrote:
 
 >     Confirmed. Assuming the code is legal, it is a regression
 >     from 3.0, which compiled it fine. A simpler code is this:
 
 This is deliberate, and the subject of previous mistaken PRs.  Compound
 literals are, in C99, unnamed variables, not constant expressions that can
 be used in initializers, and allowing them in initializers is not
 consistent with the C language and this C99 concept.  There is a special
 allowance for the old GNU "constructor expressions", which used the same
 syntax but had different semantics in this area, in gnu89 mode, but not
 gnu99.
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2002-12-03  0:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 16:46 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04 17:16 Kipp Cannon
2002-12-03 11:39 bangerth
2002-12-03 11:36 Joseph S. Myers
2002-12-03  7:06 Wolfgang Bangerth
2002-12-02 13:21 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=20021203004602.1491.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --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).