Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA PATCH] Constify strings in tracepoint.c, lookup_cmd and the completers.
Date: Wed, 13 Mar 2013 17:22:00 -0000	[thread overview]
Message-ID: <5140B5E2.7010701@redhat.com> (raw)
In-Reply-To: <20130313123205.31184.43525.stgit@brno.lan>

On 03/13/2013 05:32 AM, Pedro Alves wrote:
> This is sort of a continuation of Keith's parse_exp_1 constification
> patch.

Super!

> That ended up constifying lookup_cmd/add_cmd and (lots of) friends,
> and the completers.

Excellent. That's the one area I didn't get around to touching.

> I didn't try to constify the command hooks themselves, because I know
> upfront there are commands that write to the command string argument,
> and I think I managed to stop at a nice non-hacky split point already.

Yeah, there are a lot of places where "goofy" (old-skool?) stuff like 
this happens, e.g., strip_bg_char. Yick.

> I think the only non-really-super-obvious changes are
> tracepoint.c:validate_actionline, and tracepoint.c:trace_dump_actions.

Those look okay to me.

The only thing "wrong" that I found was missing comment on the new 
output_command_const; just to be maintainer-pedantic (even though I am 
not a maintainer). :-P

I say, commit it!

When I'm done rebasing my current work, I'll see if I can dig up the 
rest of my patches on this subject.

Keith


  reply	other threads:[~2013-03-13 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 12:32 Pedro Alves
2013-03-13 17:22 ` Keith Seitz [this message]
2013-03-13 17:29 ` Tom Tromey
2013-03-13 18:31   ` Pedro Alves

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=5140B5E2.7010701@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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