From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16927 invoked by alias); 1 Aug 2008 09:53:48 -0000 Received: (qmail 16915 invoked by uid 22791); 1 Aug 2008 09:53:46 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 01 Aug 2008 09:53:26 +0000 Received: from HOME-C4E4A596F7 ([84.229.228.238]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K4X00DQF258KDN0@i_mtaout2.012.net.il> for gdb@sources.redhat.com; Fri, 01 Aug 2008 12:53:32 +0300 (IDT) Date: Fri, 01 Aug 2008 09:53:00 -0000 From: Eli Zaretskii Subject: Re: GDB to C++ issue: deletion In-reply-to: <200808011054.24219.apoenitz@trolltech.com> X-012-Sender: halo1@inter.net.il To: =?iso-8859-1?q?Andr=E9_P=F6nitz?= Cc: gdb@sources.redhat.com Reply-to: Eli Zaretskii Message-id: References: <200807312204.m6VM4JQM007611@tully.CS.Berkeley.EDU> <200808011054.24219.apoenitz@trolltech.com> X-IsSubscribed: yes 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-08/txt/msg00002.txt.bz2 > From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= > Date: Fri, 1 Aug 2008 10:54:20 +0200 > > [1] Of course, every now and then a Guru level coder shows up, replaces > one central trouble maker with something very cool, more efficient, > even more hand-crafted, that happens to work well without being > understood by aynone else. Then the Guru leaves, and the code becomes > a "no go" area for mere mortals... Which is why we should request that every such guru documents her code, both in the sources and in gdbint.texinfo, to the level where mere mortals can hack on it later. Unfortunately, not all of them comply. Still, I think that it is a misrepresentation to say that GDB code cannot be understood by "mere mortals". Most problems, as far as I remember from questions posted here, are about the high-level architectural aspects, asked by those who want to add support for some novel or unusual platform. People who need to fix a bug in existing code normally don't have much trouble understanding it.