From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32456-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 5543 invoked by alias); 14 Jul 2008 17:54:39 -0000
Received: (qmail 5532 invoked by uid 22791); 14 Jul 2008 17:54:38 -0000
X-Spam-Check-By: sourceware.org
Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jul 2008 17:54:21 +0000
Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) 	by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id m6EHqcTt007831; 	Mon, 14 Jul 2008 19:52:38 +0200 (CEST)
Received: (from kettenis@localhost) 	by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id m6EHqcVM026983; 	Mon, 14 Jul 2008 19:52:38 +0200 (CEST)
Date: Mon, 14 Jul 2008 17:54:00 -0000
Message-Id: <200807141752.m6EHqcVM026983@brahms.sibelius.xs4all.nl>
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vladimir@codesourcery.com
CC: dewar@adacore.com, gdb@sources.redhat.com
In-reply-to: <200807142023.04952.vladimir@codesourcery.com> (message from 	Vladimir Prus on Mon, 14 Jul 2008 20:23:04 +0400)
Subject: Re: Move GDB to C++ ?
References: <487658F7.1090508@earthlink.net> <200807141953.31008.vladimir@codesourcery.com> <487B78B9.2090206@adacore.com> <200807142023.04952.vladimir@codesourcery.com>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-07/txt/msg00170.txt.bz2

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Mon, 14 Jul 2008 20:23:04 +0400
>
> > Proper documentation is always a good thing, so to the extent that the
> > current issues are to do with undocumented stuff, I would fix them by
> > providinng the documentation before deciding that switching to another
> > language will magically fix the failure to document things well.
> 
> The problem is the book named "The C++ Programming Language" went
> through at least 3 revisions, presumably with extra help of
> professional editors. Do we want to beat that? And why newcomers who
> already read this book should read the documentation for our
> non-standard mechanisms.

Oh, I think I have a copy of that book somewhere.  It's heavy enough
to kill a decent-sized bird with.  It has at least an order of
magnitude more pages than the book I learnt C from.  And I doubt it
can replace a significant fraction of the GDB internals documentation.