This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/14912] Do not print default template arguments in error messages


------- Additional Comments From gdr at integrable-solutions dot net  2005-03-26 15:55 -------
Subject: Re:  Do not print default template arguments in error messages

"dave at boost-consulting dot com" <gcc-bugzilla@gcc.gnu.org> writes:

| ------- Additional Comments From dave at boost-consulting dot com  2005-03-26 12:57 -------
| Subject: Re:  Do not print default template arguments in error messages
| 
| "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> writes:
| 
| > ------- Additional Comments From gdr at integrable-solutions dot net  2005-03-26 04:13 -------
| > Subject: Re:  Do not print default template arguments in error messages
| >
| > "dave at boost-consulting dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| >
| > [...]
| >
| > | Please, I'm begging you not to go down this road.  GCC is one of the
| >
| > I know you have strong opinions on what compilers should print; we had
| > part of this discussions on -core and it did not seem like that was a
| > universal solution that handles all the cases.  
| 
| First, I don't know if I've misunderstood what you meant by "show how
| it was written,"

If user writes vector<int>, I would like to print vector<T> [with T = int],
not vector<int>, <default> > (or variants).  Similarly, if user
wirtes vector<int, allocator<int> >, then ideally I would also like to
print vector<T, Allocator> [with T = int, Allocator = alloctor<int>].

There are discussions about carret diagnostics, but this is not it.

[...]

| > I'm going to scheme that handle the majority of the cases right.
| 
| Assuming your intention is to do what I fear (otherwise, please ignore
| the rest):

I can't ignore ignore the rest, not because I'm goiing to do something
stupid but because you also request to tke what you're saying
"seriously".  And also, because, I'm a bit fed up of your arrogance.

[...]

| > | only compilers that gets it right today (VC8 will follow), and all
| > | the ones that try to follow the "show how it was written" rule
| > | often give errors that are, for all practical purposes, unusable.
| > | If you make GCC work like the others, it will be a leap backwards
| > | and a terrible disservice to users.
| >
| > yes, you're entitled to your opinions.
| 
| This is very disappointing.  Condescencion is entirely uncalled for.

oh really?  when people try to do things, you immediately think or
"fear" that they are going to do the wrong thing.  Oh yeah, that is
not called "condescencion", you're just feeling they are stupid.

| I won't claim to know what your level of expertise is, but I know I've
| done more comparative research on template-related error messages than
| most people.  If you care about GCC's usability you ought at least to
| take what I say seriously.

Oh, I do read what you write -- everytime I have the chance.  
I know also from experience usually it is probably good not to say
anything contrary to your opinions.  But I can't resist, especially
when you don't quite understand the variations. 

-- Gaby


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]