From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20341 invoked by alias); 28 Jun 2009 18:16:44 -0000 Received: (qmail 20333 invoked by uid 22791); 28 Jun 2009 18:16:43 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 28 Jun 2009 18:16:38 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KLY00J00O2ROJ00@i_mtaout3.012.net.il> for gdb-patches@sources.redhat.com; Sun, 28 Jun 2009 21:16:35 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.213.34]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KLY00MUIO3M9PP0@i_mtaout3.012.net.il>; Sun, 28 Jun 2009 21:16:35 +0300 (IDT) Date: Sun, 28 Jun 2009 18:16:00 -0000 From: Eli Zaretskii Subject: Re: [patch] Remove unimplemented MI commands [Re: Learn function name by its address] In-reply-to: To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Reply-to: Eli Zaretskii Message-id: <83ljnc441o.fsf@gnu.org> References: <8ac60eac0906271144k61bbb6e3sc092d2780dc4192e@mail.gmail.com> <83prcp4dci.fsf@gnu.org> <8ac60eac0906271350o544d5f73i646caa1d29eb24a0@mail.gmail.com> <83ocs93v20.fsf__10960.3112018251$1246159141$gmane$org@gnu.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00789.txt.bz2 > From: Vladimir Prus > Date: Sun, 28 Jun 2009 10:42:04 +0400 > > > But in any case, no, there's no consistency issue here: while most > > humans read the code, almost no one reads the Texinfo sources of the > > docs. People read the manual in its Info, HTML, or PDF formats, where > > the @ignore'd parts are gone. > > But is there any value in keeping those (fairly useless) docs commented out > in texinfo source? The changes that most of them will be revived is close to > zero, and reviving will require writing real docs anyway. You may be right. But keeping them does no harm, while deleting them when the time comes is easy. Meanwhile, they might serve as design guidelines if someone needs that. In addition -- and to me this is no small thing -- they pay respect to the original GDB/MI designers, some of whom are still among us.