From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21424 invoked by alias); 26 Jul 2008 17:10:45 -0000 Received: (qmail 21413 invoked by uid 22791); 26 Jul 2008 17:10:44 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 26 Jul 2008 17:10:04 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6QHA0mN028972; Sat, 26 Jul 2008 13:10:00 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6QHA0n4013274; Sat, 26 Jul 2008 13:10:00 -0400 Received: from opsy.redhat.com (vpn-10-41.bos.redhat.com [10.16.10.41]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6QHA0ev007855; Sat, 26 Jul 2008 13:10:00 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 9D00937824B; Sat, 26 Jul 2008 11:09:59 -0600 (MDT) To: Eli Zaretskii Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org Subject: Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support References: <20080615181833.uxmo25mg0kko40kw@imap.linux.ibm.com> <1216107418.14956.27.camel@localhost.localdomain> <1216245620.12209.18.camel@localhost.localdomain> <20080718195010.GA14356@caradoc.them.org> <1216653969.31797.6.camel@localhost.localdomain> <20080726134252.GA6077@caradoc.them.org> <20080726144138.GA9711@caradoc.them.org> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Sat, 26 Jul 2008 17:10:00 -0000 In-Reply-To: <20080726144138.GA9711@caradoc.them.org> (Daniel Jacobowitz's message of "Sat\, 26 Jul 2008 10\:41\:38 -0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2008-07/txt/msg00481.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: >> My rationale is simple: we should have a single chapter for scripting, >> because that's where a reader would look for information on how to >> write GDB scripts. If there's sense to distributing this information >> between separate chapters, please explain what that is. Daniel> Ok, in that case I have an alternative suggestion: how about renaming Daniel> the combined scripting chapter, and putting both Python scripting and Daniel> the existing information in the new chapter? I don't really want to merge them. I don't think it provides much benefit to the reader of the manual. It might make sense to document the "python" command alongside "define" or what have you -- but I think only barely, since the "python" command is kinda pointless without the rest of the API. In the long run the Python chapter is going to be 99% documentation of the Python API, something that will hold little interest to the casual gdb user. I guess we could even go so far as to make a separate python API manual. That seemed like more of a pain though; I wasn't sure what the benefit of that would be either. Tom