This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/14912] Do not print default template arguments in error messages
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Mar 2005 04:06:43 -0000
- Subject: [Bug c++/14912] Do not print default template arguments in error messages
- References: <20040410193158.14912.schnetter@aei.mpg.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at integrable-solutions dot net 2005-03-26 04:06 -------
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:35 -------
| (In reply to comment #12)
|
| > Look at the most general template and same_type_p() with any default
| > type.
|
| How can it work? The default parameter can be dependent on previous template
| parameters. For instace, in vector, the default type in the most general
| template would be something like std::allocator<T> (with T being a previous
| template parameter), while the type in the instantiation is something like
| std::allocator<int>.
|
| > Again that is better done with cxx-pretty-print.c
|
| I don't know what cxx-pretty-print.c is, exactly.
cp/cxx-pretty-print.c
| Is it currently used?
Yes. Curently, the pretty-printing job is done by both error.c and
cxx-pretty-print.c. But, the goal is to move the codes to the latter.
| Everytime I step with GDB into an error()/warning()/info() call I only see code
| from errors.c being used. My current patch is modifying errors.c because that
| is what the FE currently uses, as far as I can tell.
you're just mistaken. I have been modifying the codes for long time
now, and I have an idea of the code path.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912