From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25365 invoked by alias); 18 Feb 2003 21:39:43 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 25357 invoked from network); 18 Feb 2003 21:39:42 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 18 Feb 2003 21:39:42 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1024C2D37 for ; Tue, 18 Feb 2003 16:44:31 -0500 (EST) Message-ID: <3E52A93E.70805@redhat.com> Date: Tue, 18 Feb 2003 21:39:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: Merge gdbarch.sh and doc/gdbint.texinfo? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00384.txt.bz2 Hello, (ok, silly idea of the day) At present the architecture vector is documented in two places: - doc/gdbinit.texinfo - gdbarch.sh What do people think of moveing gdbarch.sh's table of methods into gdbinit.texinfo and have gdbarch.sh extract them from there? It would, if nothing else, get rid of the `you need documentation' problem :-) As a kind of related side effect, what do people think of making the architecture vector table an appendix. That way it doesn't clutter up the core internals documentation. Andrew