public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: James L Peterson <peterson@austin.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/3028: 3.0 Compiler complains about template that used to work under 2.95 Date: Fri, 01 Jun 2001 12:26:00 -0000 [thread overview] Message-ID: <20010601192600.31409.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/3028; it has been noted by GNATS. From: James L Peterson <peterson@austin.ibm.com> To: Alexandre Oliva <aoliva@redhat.com> Cc: Artem Khodush <artem@duma.gov.ru>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: c++/3028: 3.0 Compiler complains about template that used to work under 2.95 Date: Fri, 01 Jun 2001 14:17:39 -0500 Alexandre Oliva wrote: > > If 3.0 is correct, from a language point of view, then this would be a > > candidate for the list of known bugs at > > http://gcc.gnu.org/bugs.html#known > > I beg to differ. That page is for actual bugs, or for non-bugs that > lots of people perceive as bugs. The problem you report is neither. I would suggest that this problem is the same as with the "G++ allows to access private types" bug. Both are cases where the old compiler allows (without error) a construct that the new compiler does not allow. For those of us trying to get large bodies of C++ code (that work with the old compiler) to work with the 3.0 compiler, it would help to have both of these listed **as problems with the old compiler**, not as problems with the new compiler. It seems to me that only question would be whether or not "lots of people" will run into either or both. If you believe that few people will run into this problem, then you are right. jim
next reply other threads:[~2001-06-01 12:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-01 12:26 James L Peterson [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-01 18:26 Gabriel Dos Reis 2001-06-01 18:26 Gabriel Dos Reis 2001-06-01 12:46 Alexandre Oliva 2001-06-01 11:36 Alexandre Oliva 2001-06-01 8:46 James L Peterson 2001-06-01 8:16 Artem Khodush 2001-06-01 7:26 peterson
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=20010601192600.31409.qmail@sourceware.cygnus.com \ --to=peterson@austin.ibm.com \ --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).