Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "taylor, david" <david.taylor@emc.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <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 16:00:00 -0000	[thread overview]
Message-ID: <63F1AEE13FAE864586D589C671A6E18B0685D0@MX203CL03.corp.emc.com> (raw)
In-Reply-To: <83oa5v0yo1.fsf@gnu.org>

> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Eli Zaretskii

> > 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.

Thank you for taking the time to review the doc parts.

> > +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.

Good point.  Fixed.

> Also, there's a type in "asociated".

Fixed.

> > +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.

Fixed.

> > +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.

Fixed.

> The documentation parts are approved with these fixed.

Thanks.  I'll repost once the non doc parts are reviewed.

> >    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.

Good catch.  Fixed.

> > +Options:\n\
> > +  -at          Use LOCATION rather than the current PC for selecting
> macros.\n\
> 
> "Selecting" sounds not very accurate.  Wouldn't "expanding" be better?

Changed.

Thanks.


  reply	other threads:[~2016-07-18 16:00 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
2016-07-18 16:00   ` taylor, david [this message]
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=63F1AEE13FAE864586D589C671A6E18B0685D0@MX203CL03.corp.emc.com \
    --to=david.taylor@emc.com \
    --cc=eliz@gnu.org \
    --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