public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/18028] nested calls to template constructors generate incorrect result Date: Sat, 16 Oct 2004 15:26:00 -0000 [thread overview] Message-ID: <20041016152626.24251.qmail@sourceware.org> (raw) In-Reply-To: <20041015215108.18028.bill@graysoft.com> ------- Additional Comments From bangerth at dealii dot org 2004-10-16 15:26 ------- Yes, to be more specific: in this situation ------------- struct X { template <typename T> X(T t); }; int main () { X x; X y(x); } ------------- the compiler has to generate a copy constructor itself, the template copy constructor is only used for arguments T which are not of type X. You will want to have an additional, non-template constructor. W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18028
prev parent reply other threads:[~2004-10-16 15:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-15 21:51 [Bug c++/18028] New: " bill at graysoft dot com 2004-10-15 22:49 ` [Bug c++/18028] " pinskia at gcc dot gnu dot org 2004-10-16 15:26 ` bangerth at dealii dot org [this message]
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=20041016152626.24251.qmail@sourceware.org \ --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: 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).