public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mrs@wrs.com (Mike Stump)
To: als@tusc.com.au
Cc: egcs@cygnus.com
Subject: Re: error message formatting
Date: Wed, 15 Apr 1998 14:53:00 -0000	[thread overview]
Message-ID: <199804151902.MAA19163@kankakee.wrs.com> (raw)

> From: Anthony Shipman <als@tusc.com.au>
> Date: Wed, 15 Apr 1998 03:50:00 +1000 (EST)

> It would be nice if there was some readable formatting for error messages 
> instead of the following.  There are three very long lines here.

> fxg_glyph_mgr.cc:345: no matching function for call to `map<int,list<FXG_Glyph *,__default_alloc_template<false,0> > *,less<int>,__default_alloc_template<false,0> >::insert (__rb_tree_iterator<pair<const int,list<FXG_Glyph *,__default_alloc_template<false,0> > *>,pair<const int,list<FXG_Glyph *,__default_alloc_template<false,0> > *> &,pair<const int,list<FXG_Glyph *,__default_alloc_template<false,0> > *> *> &, list<FXG_Glyph *,__default_alloc_template<false,0> > *&)'

To be concrete, I think if we check to see if the type of a template
parameter is the default value for the parameter, it be not printed
if it would have been the last one printed.

Also, if there exists a typedef name for a type, then we use the
typedef name instead of the real name, if the real name is a template
of some kind.

             reply	other threads:[~1998-04-15 14:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-15 14:53 Mike Stump [this message]
1998-04-15 20:39 ` Joe Buck
1998-04-16 10:51   ` Per Bothner
1998-04-16 13:53     ` Joe Buck
1998-04-16  5:58 ` David Cogen
  -- strict thread matches above, loose matches on Subject: below --
1998-04-20 11:44 Kaz Kylheku
1998-04-16 14:20 Mike Stump
1998-04-14 15:23 Anthony Shipman
1998-04-15  7:39 ` David Cogen
1998-04-15 14:53   ` Mark Schaefer
1998-04-15 14:53     ` David Cogen
1998-04-15 23:03       ` Joe Buck
1998-04-16  6:10         ` David Cogen
1998-04-16  2:26       ` Per Bothner
1998-04-16 16:34       ` Anthony Shipman
1998-04-17  2:23         ` Pieter Nagel
1998-04-17 14:42         ` David Cogen
1998-04-15 23:03     ` Joe Buck
1998-04-16 16:34   ` Craig Burley
1998-04-15 14:53 ` Joe Buck
1998-04-16  0:01   ` Mark Mitchell
1998-04-16 18:39     ` Alexandre Oliva
1998-04-16 23:59       ` Mark Mitchell
1998-04-16  5:58   ` David Cogen
1998-04-16 13:53     ` David Cogen
1998-04-21 17:06   ` Lassi A. Tuura

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=199804151902.MAA19163@kankakee.wrs.com \
    --to=mrs@wrs.com \
    --cc=als@tusc.com.au \
    --cc=egcs@cygnus.com \
    /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).