From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27581 invoked by alias); 24 May 2014 04:42:40 -0000 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 Received: (qmail 27559 invoked by uid 89); 24 May 2014 04:42:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yh0-f53.google.com Received: from mail-yh0-f53.google.com (HELO mail-yh0-f53.google.com) (209.85.213.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Sat, 24 May 2014 04:42:38 +0000 Received: by mail-yh0-f53.google.com with SMTP id i57so4940542yha.26 for ; Fri, 23 May 2014 21:42:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.44.41 with SMTP id m29mr13703180yhb.57.1400906556510; Fri, 23 May 2014 21:42:36 -0700 (PDT) Received: by 10.170.150.70 with HTTP; Fri, 23 May 2014 21:42:36 -0700 (PDT) In-Reply-To: <83lhttn88w.fsf@gnu.org> References: <83lhttn88w.fsf@gnu.org> Date: Sat, 24 May 2014 04:42:00 -0000 Message-ID: Subject: Re: [PATCH, doc RFA]: Add guile progspace support From: Doug Evans To: Eli Zaretskii Cc: "gdb-patches@sourceware.org" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00613.txt.bz2 On Thu, May 22, 2014 at 8:27 AM, Eli Zaretskii wrote: >> From: Doug Evans >> Date: Wed, 21 May 2014 12:22:20 -0700 >> >> This patch adds guile progspace support. > > Thanks. > >> +@deffn {Scheme Procedure} progspace-filename progspace >> +Return the file name of @var{progspace} as a string. >> +If the program space does not have an associated file name, >> +then @code{#f} is returned. This occurs, for example, when @value{GDBN} >> +is started without a program to debug. > > I guess this is the file name of the executable program running in the > progspace? If so, why not tell that explicitly? This text as written > begs the question what file is named by that string. Also, is the > file absolute, relative, something else? Is it just the value of > argv[0] in that program? Etc. etc. I'll work on improving the text. However, I wish to point out that the python version says this: @defvar Progspace.filename The file name of the progspace as a string. @end defvar I have to say it's a bit disappointing that if there were issues with this text that they weren't addressed the first time.