public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at boost-consulting dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/25185] deep typedef substitution in error message
Date: Thu, 09 Apr 2009 13:58:00 -0000	[thread overview]
Message-ID: <20090409135809.30670.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25185-501@http.gcc.gnu.org/bugzilla/>



------- Comment #31 from dave at boost-consulting dot com  2009-04-09 13:58 -------
OK, I don't get what it's controlling then, but maybe that's not important. 
Still, I suggest you choose a more specific name to leave the door open for
"prettier" template printing in the future.  If you did introduce indenting or
other prettification that wasn't controlled by this option, it would be
confusing.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25185


  parent reply	other threads:[~2009-04-09 13:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 17:47 [Bug c++/25185] New: " dave at boost-consulting dot com
2005-11-30 17:48 ` [Bug c++/25185] " dave at boost-consulting dot com
2008-11-06 20:01 ` dave at boost-consulting dot com
2008-11-06 20:21 ` dgregor at gcc dot gnu dot org
2009-03-02 16:20 ` jason at gcc dot gnu dot org
2009-03-02 16:39 ` dave at boost-consulting dot com
2009-03-02 17:01 ` jason at gcc dot gnu dot org
2009-03-02 18:25 ` jason at gcc dot gnu dot org
2009-03-02 18:25 ` jason at gcc dot gnu dot org
2009-03-02 20:24 ` dave at boost-consulting dot com
2009-03-02 20:35 ` jason at redhat dot com
2009-03-02 20:43 ` jason at redhat dot com
2009-04-02 21:39 ` jason at gcc dot gnu dot org
2009-04-02 21:52 ` jason at gcc dot gnu dot org
2009-04-02 21:53 ` jason at gcc dot gnu dot org
2009-04-03 14:09 ` jason at gcc dot gnu dot org
2009-04-03 19:38 ` dave at boost-consulting dot com
2009-04-03 20:52 ` jason at gcc dot gnu dot org
2009-04-03 20:57 ` jason at gcc dot gnu dot org
2009-04-03 21:46 ` jason at gcc dot gnu dot org
2009-04-04  1:33 ` dave at boostpro dot com
2009-04-04  3:46 ` jason at redhat dot com
2009-04-04 19:19 ` jason at gcc dot gnu dot org
2009-04-06  9:36 ` dave at boostpro dot com
2009-04-06 15:32 ` jason at redhat dot com
2009-04-07 17:49 ` jason at gcc dot gnu dot org
2009-04-08 16:09 ` jason at gcc dot gnu dot org
2009-04-08 19:32 ` jason at gcc dot gnu dot org
2009-04-08 19:38 ` jason at gcc dot gnu dot org
2009-04-08 19:49 ` dave at boost-consulting dot com
2009-04-09  2:10 ` jason at redhat dot com
2009-04-09 13:58 ` dave at boost-consulting dot com [this message]
2009-11-03 20:40 ` 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=20090409135809.30670.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: 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).