From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17443 invoked by alias); 19 Feb 2003 13:01:17 -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 17435 invoked from network); 19 Feb 2003 13:01:16 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 19 Feb 2003 13:01:16 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 17F322D37; Wed, 19 Feb 2003 08:06:03 -0500 (EST) Message-ID: <3E53813A.8050401@redhat.com> Date: Wed, 19 Feb 2003 13:01: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: Zaretskii Eli Cc: gdb-patches@sources.redhat.com Subject: Re: Merge gdbarch.sh and doc/gdbint.texinfo? References: <4D19136444628A40840EFE8C5AE04147017A33@ELTIMAIL1.elta.co.il> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00399.txt.bz2 (yes I probably should have sent this to gdb@) >> From: Andrew Cagney [mailto:ac131313@redhat.com] >> Sent: Tuesday, February 18, 2003 11:45 PM >> >> What do people think of moving gdbarch.sh's table of methods into >> gdbinit.texinfo and have gdbarch.sh extract them from there? > > > I'm all for it. There is an `obvious' follow on to this. The target, along with some other vectors, could also be put into separate appendicies. > 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. What about this? My guess at what to do next is: - move the arch vector to the appendix and make it a separate file - change it to use that weird @defun texi thingie - add in the missing methods - finally start worrying about the doco Andrew