From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11444 invoked by alias); 26 Mar 2005 04:14:05 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 11423 invoked by alias); 26 Mar 2005 04:14:01 -0000 Date: Sat, 26 Mar 2005 04:14:00 -0000 Message-ID: <20050326041401.11422.qmail@sourceware.org> From: "gdr at integrable-solutions dot net" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040410193158.14912.schnetter@aei.mpg.de> References: <20040410193158.14912.schnetter@aei.mpg.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/14912] Do not print default template arguments in error messages X-Bugzilla-Reason: CC X-SW-Source: 2005-03/txt/msg03063.txt.bz2 List-Id: ------- 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" 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. I'm going to scheme that handle the majority of the cases right. | 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. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912