public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: llib@computer.org To: gcc-gnats@gcc.gnu.org Subject: c++/7768: __PRETTY_FUNCTION__ for template destructor is wrong Date: Thu, 29 Aug 2002 19:36:00 -0000 [thread overview] Message-ID: <200208300147.LAA03127@bullet.anu.edu.au> (raw) >Number: 7768 >Category: c++ >Synopsis: __PRETTY_FUNCTION__ for template destructor is wrong >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Aug 29 18:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Bill Clarke >Release: 3.1.1 >Organization: Australian National University >Environment: System: SunOS bullet 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-5_10 Architecture: sun4 host: sparc-sun-solaris2.8 build: sparc-sun-solaris2.8 target: sparc-sun-solaris2.8 configured with: ../gcc-3.1.1/configure --with-cpu=ultrasparc --enable-lanaguages=c,c++,f77 : (reconfigured) ../gcc-3.1.1/configure --with-cpu=ultrasparc --enable-languages=c,c++,f77 >Description: __PRETTY_FUNCTION__ in a destructor of a template looks like a constructor that returns void and takes no args: e.g., this code: // begins #include <iostream> template <typename T> struct X { X() { std::cout << __PRETTY_FUNCTION__ << std::endl; } ~X() { std::cout << __PRETTY_FUNCTION__ << std::endl; } }; int main() { { X<int> x; } return 0; } // ends when compiled and executed produces: X<T>::X() [with T = int] void X<T>::X() [with T = int] >How-To-Repeat: compile and run above code with g++ >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-30 1:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-29 19:36 llib [this message] 2002-09-13 13:41 nathan 2002-09-14 12:17 nathan 2002-09-14 16:24 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=200208300147.LAA03127@bullet.anu.edu.au \ --to=llib@computer.org \ --cc=gcc-gnats@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).