From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10166 invoked by alias); 26 Nov 2003 21:44:12 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10153 invoked from network); 26 Nov 2003 21:44:12 -0000 Received: from unknown (HELO tisch.mail.mindspring.net) (207.69.200.157) by sources.redhat.com with SMTP; 26 Nov 2003 21:44:12 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AP7Rm-0000FY-00; Wed, 26 Nov 2003 16:43:42 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 626764B40B; Wed, 26 Nov 2003 16:43:41 -0500 (EST) To: drow@mvista.com, ian@wasabisystems.com Subject: Re: C++/Java regressions Cc: gdb@sources.redhat.com Message-Id: <20031126214341.626764B40B@berman.michael-chastain.com> Date: Wed, 26 Nov 2003 21:44:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-11/txt/msg00269.txt.bz2 ian> Yes, I think it should print A::bar without the const. I have the ian> patch in my sources, but I haven't checked it in yet. But what about: class Foo { public: int method (); int method () const; }; If the name comes back as "Foo::method" then we have ambiguity in gdb's output. I think the const looks ugly and the code that prints the function name is also ugly. But I don't wanna print the same name for two different methods. Michael C