From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14373 invoked by alias); 14 Jul 2008 16:31:52 -0000 Received: (qmail 14363 invoked by uid 22791); 14 Jul 2008 16:31:51 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 16:31:33 +0000 Received: (qmail 14186 invoked from network); 14 Jul 2008 16:31:31 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 14 Jul 2008 16:31:31 -0000 From: Vladimir Prus To: Daniel Jacobowitz Subject: Re: Move GDB to C++ ? Date: Mon, 14 Jul 2008 16:31:00 -0000 User-Agent: KMail/1.9.9 Cc: Robert Dewar , gdb@sources.redhat.com References: <487658F7.1090508@earthlink.net> <200807141953.31008.vladimir@codesourcery.com> <20080714161228.GA3833@caradoc.them.org> In-Reply-To: <20080714161228.GA3833@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807142031.29811.vladimir@codesourcery.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00164.txt.bz2 On Monday 14 July 2008 20:12:28 Daniel Jacobowitz wrote: > On Mon, Jul 14, 2008 at 07:53:30PM +0400, Vladimir Prus wrote: > > I think that in this case, the most important argument is that GDB already > > uses most of the features C++ has to offer -- except in non-standard and > > undocumented way. Switch to C++ will make that better. The only price to > > pay is requiring C++ compiler -- and given that the GNU project makes GCC, > > I just don't see the issue. > > Consider requiring the C++ runtime, then... this would be a problem > for CodeSourcery in the same way that it would be for AdaCore. > Solvable in both cases, and I have no qualms about solving it, but it > will be some work. I recall we have this problem solved ;-) We did not actually push that to the field, since we prototyped it with a library, which a customer might link into a application with different libstdc++, but GDB, been a binary, would not have that issue. - Volodya