This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: error message formatting
- To: als at tusc dot com dot au
- Subject: Re: error message formatting
- From: mrs at wrs dot com (Mike Stump)
- Date: Wed, 15 Apr 1998 12:02:41 -0700
- Cc: egcs at cygnus dot com
> 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.