From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add '-at location' support to 'macro expand', 'macro expand-once', 'info macro', 'ptype', and 'whatis' commands.
Date: Mon, 18 Jul 2016 15:11:00 -0000 [thread overview]
Message-ID: <83oa5v0yo1.fsf@gnu.org> (raw)
In-Reply-To: <24519.1468851836@usendtaylorx2l> (message from David Taylor on Mon, 18 Jul 2016 10:23:56 -0400)
> From: David Taylor <dtaylor@emc.com>
> Date: Mon, 18 Jul 2016 10:23:56 -0400
>
> Add '-at location' support to 'macro expand', 'macro expand-once', 'info
> macro', 'ptype', and 'whatis' commands.
Thanks.
> +it can be any string of tokens. If the optional @var{location} is
> +specified, it is used to determine which macro definitions are in
> +scope; otherwise, as before, it uses the source and line asociated with
> +the current program counter.
Please lose the "as before" part, it is not appropriate for the
manual, since we always describe the current state of events.
Also, there's a type in "asociated".
> +can be any string of tokens. If the optional @var{location} is
> +specified, it is used to determine which macro definitions are in
> +scope; otherwise, as before, it uses the source and line asociated with
> +the current program counter.
Likewise.
> +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. If the optional
> +@var{location} is specified, it is used to determine which definition,
> +if any, of the macro is in scope; otherwise, as before, it uses the
> +source and line asociated with the current program counter.
Likewise.
The documentation parts are approved with these fixed.
> add_cmd ("expand", no_class, macro_expand_command, _("\
> Fully expand any C/C++ preprocessor macro invocations in EXPRESSION.\n\
> -Show the expanded expression."),
> +Show the expanded expression.\n\
> +Usage: macro expand [-at LCOATION,] [--] EXPR\n\
^^^^^^^^
Typo.
> +Options:\n\
> + -at Use LOCATION rather than the current PC for selecting macros.\n\
"Selecting" sounds not very accurate. Wouldn't "expanding" be better?
next prev parent reply other threads:[~2016-07-18 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:24 David Taylor
2016-07-18 15:11 ` Eli Zaretskii [this message]
2016-07-18 16:00 ` taylor, david
2016-08-02 11:17 ` Andrew Burgess
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=83oa5v0yo1.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