public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mueller@kde.org,
	nobody@gcc.gnu.org
Subject: Re: c++/9537: [3.4 regression] [New parser] problem handling const return types
Date: Sun, 02 Feb 2003 22:32:00 -0000	[thread overview]
Message-ID: <20030202223213.21747.qmail@sources.redhat.com> (raw)

Synopsis: [3.4 regression] [New parser] problem handling const return types

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Sun Feb  2 22:32:13 2003
State-Changed-Why:
    Confirmed. I would say the code is legal, and even if not
    then it is certainly true that the error message absolutely
    does not make sense at all.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9537


             reply	other threads:[~2003-02-02 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:32 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-05 21:11 jason
2003-02-03 16:26 Wolfgang Bangerth
2003-02-03  1:36 Dirk Mueller
2003-02-01 21:06 mueller

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=20030202223213.21747.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mueller@kde.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).