From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19457 invoked by alias); 6 Sep 2011 19:45:31 -0000 Received: (qmail 19446 invoked by uid 22791); 6 Sep 2011 19:45:31 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Sep 2011 19:45:14 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0LR400J009AM9Y00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Tue, 06 Sep 2011 22:43:12 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.83.44]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LR400IEE9FY1PF0@a-mtaout22.012.net.il>; Tue, 06 Sep 2011 22:43:11 +0300 (IDT) Date: Tue, 06 Sep 2011 19:56:00 -0000 From: Eli Zaretskii Subject: Re: Doc: make python function/method descriptions look as in Python In-reply-to: To: pmuldoon@redhat.com Cc: Paul_Koning@Dell.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <837h5ljw31.fsf@gnu.org> References: <09787EF419216C41A903FD14EE5506DD015343BFAE@AUSX7MCPC103.AMER.DELL.COM> <837h5p2a6g.fsf@gnu.org> <09787EF419216C41A903FD14EE5506DD01534911A3@AUSX7MCPC103.AMER.DELL.COM> <09787EF419216C41A903FD14EE5506DD01534916A6@AUSX7MCPC103.AMER.DELL.COM> 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: 2011-09/txt/msg00095.txt.bz2 > From: Phil Muldoon > Cc: > Date: Tue, 06 Sep 2011 20:36:14 +0100 > > writes: > > > Here is an updated version. This one replaces defmethod by defun and defivar by defvar, with the class name explicit on the symbol as is the Python documentation convention. I'm sending the diff as an attachment, hope that works right. > > I think it is great. If Eli is fine with it, and it meets the standards > of the GDB manual, I think it would be an improvement. I'm fine with it, if Paul decided not to do anything about collapsing @r{]}@r{]} and the slanted parentheses look okay in print.