From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: info macro [-at LOCATION,]
Date: Tue, 11 Nov 2014 03:44:00 -0000 [thread overview]
Message-ID: <83mw7ymmdw.fsf@gnu.org> (raw)
In-Reply-To: <31913.1415655693@usendtaylorx2l>
> From: David Taylor <dtaylor@emc.com>
> Date: Mon, 10 Nov 2014 16:41:33 -0500
>
> A few releases ago it was possible to set a location that would be used
> by 'info location' by typing something like:
>
> list file.c:42
>
> and then do:
>
> info macro MACRONAME
>
> . Sometime between release 7.1 and 7.8 that stopped working.
>
> The following patch adds the option [-at LOCATION,] to 'info macro' to
> enable the use of a user selected location as a documented feature.
>
> Three files, three change log entries:
Thanks. I think this warrants a NEWS entry as well.
> gdb/doc/ChangeLog:
>
> 2014-11-10 David Taylor <dtaylor@emc.com>
>
> * gdb.texinfo: Document new -at LOCATION option of the 'info
> macro' command.
Please state the node in which the change was made (as if it were a
function, i.e. in parentheses).
> -@item info macro [-a|-all] [--] @var{macro}
> +@item info macro [-a|-all] [-at LOCATION,] [--] @var{macro}
> Show the current definition or all definitions of the named @var{macro},
> and describe the source location or compiler command-line where that
> definition was established. The optional double dash is to signify the end of
> argument processing and the beginning of @var{macro} for non C-like macros where
> -the macro may begin with a hyphen.
> +the macro may begin with a hyphen. If the optional LOCATION is specified,
> +it is used instead of the current location.
First, "LOCATION" should be "@var{location}", as it is a parameter,
not a literal string.
And second, "it is used instead of the current location" leaves too
much unsaid. The reader will wonder why does location matter for this
purpose. I suggest to make that explicit in the text.
next prev parent reply other threads:[~2014-11-11 3:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 21:41 David Taylor
2014-11-11 3:44 ` Eli Zaretskii [this message]
2014-11-11 14:01 ` David Taylor
2014-11-11 15:41 ` Eli Zaretskii
2014-11-19 21:00 ` RFA info macro [-at LOCATION,] (v2) David Taylor
2014-11-19 21:20 ` Eli Zaretskii
2014-11-20 2:38 ` Doug Evans
[not found] ` <001a1132e59ca4575e0508413955@google.com>
[not found] ` <CAP9bCMRJr4Fbunbnt-93FYnWUgDqjaLWZ731_rZp-JP8qkKf=w@mail.gmail.com>
2014-11-20 14:58 ` Fwd: Delivery Status Notification (Failure) David Taylor
2014-11-23 19:18 ` Doug Evans
2014-11-23 20:00 ` 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=83mw7ymmdw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@emc.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).