Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFAv2 1/6] New cli-utils.h/.c function extract_info_print_args
Date: Tue, 25 Sep 2018 04:37:00 -0000	[thread overview]
Message-ID: <1537850228.1486.3.camel@skynet.be> (raw)
In-Reply-To: <87tvmfniwi.fsf@tromey.com>

On Mon, 2018-09-24 at 07:07 -0600, Tom Tromey wrote:
> Maybe it is too late to fix the "mem" command.  I am not sure.  I do
> know that back when I approved a similar change to "disasssemble" (I
> thought I'd written that!  But the history shows not), there were
> complaints -- we broke people's workarounds for the bad parsing
> behavior.  On the other hand, "disasssemble" is probably used a lot more
> than "mem".
> 
> Philippe> So, it looks possible to have extract_arg behaviour replaced by
> Philippe> extract_arg_maybe_quoted behaviour.
> Philippe> If you agree with the above analysis, I will work on that in a separate
> Philippe> patch series.
> 
> One idea might be to upgrade the calls where it seems reasonable and
> then leave the legacy behavior for the ones where it is not... perhaps
> at the end, renaming extract_arg so that the name makes it clear that it
> shouldn't be used in new code.
> 
> What do you think of that?  It's not necessary for you to do all the
> work involved.
Yes, that sounds a reasonable approach.

No problem for me to work on that, and give a proposal
'change to new behavior' or 'keep legacy behavior'  for each
extract_arg call (it might take a week or 2, as gdb is
an evening/week-end activity).

Once the analysis of which calls are reasonable to change is done,
the code
changes should be pretty small.

Philippe


  reply	other threads:[~2018-09-25  4:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 16:54 [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 3/6] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables] Philippe Waroquiers
2018-09-18 15:52   ` Tom Tromey
2018-09-23 21:34     ` Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 5/6] Announce changes in NEWS " Philippe Waroquiers
2018-08-26 18:21   ` Eli Zaretskii
2018-08-27  4:39     ` Philippe Waroquiers
2018-08-27 14:59       ` Eli Zaretskii
2018-08-26 16:54 ` [RFAv2 4/6] Document changes " Philippe Waroquiers
2018-08-26 18:19   ` Eli Zaretskii
2018-08-26 16:54 ` [RFAv2 6/6] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 2/6] Make struct type_print_options default_ptype_flags non static Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 1/6] New cli-utils.h/.c function extract_info_print_args Philippe Waroquiers
2018-09-18 15:31   ` Tom Tromey
2018-09-23 20:16     ` Philippe Waroquiers
2018-09-24 13:07       ` Tom Tromey
2018-09-25  4:37         ` Philippe Waroquiers [this message]
2018-09-06 20:16 ` PING Re: [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-09-13 19:27 ` PING^2 " Philippe Waroquiers

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=1537850228.1486.3.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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