Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA info macro [-at LOCATION,] (v2)
Date: Thu, 20 Nov 2014 02:38:00 -0000	[thread overview]
Message-ID: <CAP9bCMSET712avGFSp2yoj-F+ts6m3nfgiqd1E3zbz0V-xXpbQ@mail.gmail.com> (raw)
In-Reply-To: <8085.1416430826@usendtaylorx2l>

On Wed, Nov 19, 2014 at 1:00 PM, David Taylor
<dtaylor@usendtaylorx2l.lss.emc.com> wrote:
> This adds a NEWS entry as requested by Eli and I believe addresses his
> concerns with regard to gdb/doc/gdb.texinfo.  The other two files
> gdb/macrocmd.c and gdb/testsuite/gdb.base/info-macros.exp are unchanged
> from the previous submission.  I updated the gdb/ChangeLog entry to
> include the gdb/NEWS addition..
>
> 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.

Hi.

The "," in "-at LOCATION," seems a bit random, relative to other commands.

Maybe it is the best way to go.
If so, I'd like to see the reasons why it exists documented in the code.

Can we just remove the , and require -- when necessary?


  parent reply	other threads:[~2014-11-20  2:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 21:41 RFA: info macro [-at LOCATION,] David Taylor
2014-11-11  3:44 ` Eli Zaretskii
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 [this message]
     [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=CAP9bCMSET712avGFSp2yoj-F+ts6m3nfgiqd1E3zbz0V-xXpbQ@mail.gmail.com \
    --to=xdje42@gmail.com \
    --cc=dtaylor@usendtaylorx2l.lss.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