public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14912] Do not print default template arguments in error messages Date: Sat, 26 Mar 2005 04:04:00 -0000 [thread overview] Message-ID: <20050326040415.2552.qmail@sourceware.org> (raw) In-Reply-To: <20040410193158.14912.schnetter@aei.mpg.de> ------- Additional Comments From gdr at integrable-solutions dot net 2005-03-26 04:04 ------- Subject: Re: Do not print default template arguments in error messages "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> writes: | ------- Additional Comments From giovannibajo at libero dot it 2005-03-26 00:30 ------- | (In reply to comment #14) | | > | The first patch will deal with just removal of default | > | arguments, and I believe that the less intrusive and clean solution is to | > | display <default> in the "with" clause. | > please: | > (1) don't do an unconditional removal; | > (2) don't show <default>. | > I would oppose any patch short of that. | | Yes, the remove will be conditioned on a flag (but I believe this has to become | the default). which flag? A compiler option? I don't think a multiplication of compiler options for this stuff is a good way to go. | About the <default>, I don't understand what you are proposing as an | alternative. Are you proposing to completely remove those template parameters | from the "with" clause? when they are default, yes. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
next prev parent reply other threads:[~2005-03-26 4:04 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-10 19:55 [Bug c++/14912] New: " schnetter at aei dot mpg dot de 2004-04-10 19:55 ` [Bug c++/14912] " pinskia at gcc dot gnu dot org 2004-04-10 20:01 ` schnetter at aei dot mpg dot de 2004-04-10 21:50 ` pinskia at gcc dot gnu dot org 2004-04-10 22:40 ` gdr at integrable-solutions dot net 2005-03-23 2:45 ` giovannibajo at libero dot it 2005-03-23 4:55 ` dave at boost-consulting dot com 2005-03-23 10:51 ` giovannibajo at libero dot it 2005-03-23 11:01 ` giovannibajo at libero dot it 2005-03-23 12:55 ` dave at boost-consulting dot com 2005-03-24 2:15 ` giovannibajo at libero dot it 2005-03-25 22:07 ` gdr at integrable-solutions dot net 2005-03-25 22:09 ` gdr at integrable-solutions dot net 2005-03-25 22:09 ` gdr at integrable-solutions dot net 2005-03-25 22:12 ` gdr at integrable-solutions dot net 2005-03-26 0:31 ` giovannibajo at libero dot it 2005-03-26 0:35 ` giovannibajo at libero dot it 2005-03-26 2:01 ` dave at boost-consulting dot com 2005-03-26 4:04 ` gdr at integrable-solutions dot net [this message] 2005-03-26 4:06 ` gdr at integrable-solutions dot net 2005-03-26 4:14 ` gdr at integrable-solutions dot net 2005-03-26 11:59 ` giovannibajo at libero dot it 2005-03-26 12:57 ` dave at boost-consulting dot com 2005-03-26 15:40 ` gdr at integrable-solutions dot net 2005-03-26 15:55 ` gdr at integrable-solutions dot net 2005-03-26 16:14 ` dave at boost-consulting dot com 2005-03-26 19:24 ` giovannibajo at libero dot it 2005-03-26 19:26 ` giovannibajo at libero dot it 2005-03-26 19:52 ` gdr at integrable-solutions dot net 2005-03-26 22:58 ` bangerth at dealii dot org 2005-03-27 0:56 ` giovannibajo at libero dot it 2005-03-27 1:53 ` dave at boost-consulting dot com 2005-03-27 3:16 ` gdr at integrable-solutions dot net [not found] <bug-14912-7427@http.gcc.gnu.org/bugzilla/> 2007-10-12 11:05 ` pcarlini at suse dot de 2007-10-15 14:05 ` pluto at agmk dot net 2008-09-19 12:24 ` b0ntrict0r at yandex dot ru 2008-09-22 9:23 ` pluto at agmk dot net 2008-09-22 15:13 ` b0ntrict0r at yandex dot ru 2008-09-22 21:55 ` pluto at agmk dot net 2008-09-23 10:13 ` pluto at agmk dot net 2008-09-23 10:14 ` pluto at agmk dot net 2008-09-23 14:32 ` b0ntrict0r at yandex dot ru 2008-09-25 13:21 ` pluto at agmk dot net 2009-03-02 21:04 ` pluto at agmk dot net 2009-03-02 21:59 ` hjl dot tools at gmail dot com 2009-03-03 18:55 ` jason at gcc dot gnu dot org 2009-03-23 19:01 ` pluto at agmk dot net 2009-04-05 6:06 ` jason at gcc dot gnu dot org 2009-04-05 19:29 ` jason at gcc dot gnu dot org 2009-04-09 20:30 ` jason at gcc dot gnu dot org 2009-07-26 10:38 ` arekm at pld-linux dot org 2009-07-29 20:36 ` jason at gcc dot gnu dot org 2009-07-29 21:09 ` jason at gcc dot gnu dot org
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=20050326040415.2552.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).