public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nathan@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/383: C++v2,96:member template conversion not implicit
Date: Tue, 22 Oct 2002 15:16:00 -0000	[thread overview]
Message-ID: <20021022221603.9100.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Cc: jcampbell3@prodigy.net
Subject: Re: c++/383: C++v2,96:member template conversion not implicit
Date: Tue, 22 Oct 2002 17:14:06 -0500 (CDT)

 This bug still applies with present CVS and 3.2. A slightly simpler to 
 read form of the report is this:
 -----------------------------------------
 template <bool P> struct X {
     template <bool PP> operator X<PP>& (void);
 };
 
 int main(void) {
   X<true> x;
   static_cast<X<false> >(x);
   X<false> y = x;
 };
 -----------------------------------------
 The messages are
 y.cc: In function `int main()':
 y.cc:7: error: no matching function for call to `X<false>::X(X<true>&)'
 y.cc:1: error: candidates are: X<false>::X()
 y.cc:1: error:                 X<false>::X(const X<false>&)
 y.cc:8: error: conversion from `X<true>' to non-scalar type `X<false>'
    requested
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-10-22 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 15:16 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20 18:47 Wolfgang Bangerth
2001-12-26 10:17 nathan

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=20021022221603.9100.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nathan@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).