Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA]: Add guile progspace support
Date: Thu, 22 May 2014 15:27:00 -0000	[thread overview]
Message-ID: <83lhttn88w.fsf@gnu.org> (raw)
In-Reply-To: <m37g5fhr83.fsf@sspiff.org>

> From: Doug Evans <xdje42@gmail.com>
> 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.

> +A @code{gdb:invalid-object-error} exception is thrown if @var{PROGSPACE}
> +is invalid.                                                   ^^^^^^^^^

"progspace", in lower case.

> +@deffn {Scheme Procedure} progspace-objfiles progspace
> +Return the list of objfiles of @var{progspace}.
> +The order of objfiles in the result is arbitrary.

"Arbitrary" or in the same order they are stored in some symbol table?

> +A @code{gdb:invalid-object-error} exception is thrown if @var{PROGSPACE}
> +is invalid.                                                   ^^^^^^^^^

"progspace" in lower case.


  reply	other threads:[~2014-05-22 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 19:22 Doug Evans
2014-05-22 15:27 ` Eli Zaretskii [this message]
2014-05-24  4:42   ` Doug Evans
2014-05-24  7:31     ` Eli Zaretskii
2014-06-01 20:37   ` Doug Evans
2014-06-02 15:20     ` Eli Zaretskii
2014-06-03  6:51       ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lhttn88w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox