public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/10807] [DR 295] It should be possible to cv-qualify function types, if the CV qualifications are introduced through a typedef or a template argument
Date: Mon, 05 Apr 2004 15:54:00 -0000	[thread overview]
Message-ID: <20040405155401.2176.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030515181600.10807.giovannibajo@libero.it>


------- Additional Comments From nathan at gcc dot gnu dot org  2004-04-05 15:53 -------
reopening ...

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10807


  parent reply	other threads:[~2004-04-05 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030515181600.10807.giovannibajo@libero.it>
2003-08-03 18:14 ` [Bug c++/10807] [DR 295] It should be possible to cv-qualify references even to " neroden at gcc dot gnu dot org
2003-12-17  5:40 ` mmitchel at gcc dot gnu dot org
2003-12-18  3:37 ` [Bug c++/10807] [3.3/3.4 regression] " giovannibajo at libero dot it
2003-12-22  5:25 ` pinskia at gcc dot gnu dot org
2003-12-26 19:34 ` pinskia at gcc dot gnu dot org
2004-01-11  1:41 ` pinskia at gcc dot gnu dot org
2004-02-05  2:37 ` [Bug c++/10807] [DR 295] It should be possible to cv-qualify " mmitchel at gcc dot gnu dot org
2004-04-02 15:03 ` nathan at gcc dot gnu dot org
2004-04-05 15:54 ` nathan at gcc dot gnu dot org [this message]
2004-04-05 15:55 ` nathan at gcc dot gnu dot org

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=20040405155401.2176.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).