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++/7136: Template constants deduction
Date: Thu, 23 Jan 2003 15:06:00 -0000	[thread overview]
Message-ID: <20030123150601.25342.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: "Philippe A. Bouchard" <philippeb@videotron.ca>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/7136: Template constants deduction
Date: Thu, 23 Jan 2003 09:03:30 -0600 (CST)

 On Thu, 23 Jan 2003, Philippe A. Bouchard wrote:
 
 > Yes you're right but the following won't work either under gcc 2.95:
 > 
 > struct Type
 > {
 >  int i;
 > };
 > 
 > template <typename _T, int _T::* _I>
 >  struct Number {};
 > 
 > template <typename _T, int _T::* _I>
 >  void foo(Number<_T, _I> const &)
 >  {
 >  }
 > 
 > int main()
 > {
 >  foo(Number<Type, & Type::i>());
 > }
 > 
 > Returns:
 > template.cpp: In function `int main()':
 > template.cpp:15: no matching function for call to `foo
 > (Number<Type,&Type::i>)'
 
 True, but there's not much that we can do about it: that's simply a bug in 
 gcc2.95 that was fixed in 3.0. gcc2.95 is not maintained any more, so I 
 fear that you will have to find a workaround for gcc2.95.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-01-23 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 15:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-23  5:36 Philippe A. Bouchard
2003-01-23  3:16 bangerth
2002-07-03 12:45 nathan
2002-06-26 23:06 philippeb

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