From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches\@sourceware.org ml"
<gdb-patches@sourceware.org>
Subject: Re: [RFA] "constify" parse_exp_1
Date: Mon, 11 Mar 2013 18:30:00 -0000 [thread overview]
Message-ID: <87y5dtn61h.fsf@fleche.redhat.com> (raw)
In-Reply-To: <513E0B58.4090800@redhat.com> (Keith Seitz's message of "Mon, 11 Mar 2013 09:50:32 -0700")
Keith> Ok, that strdup, while not necessary, is not yet ready to be removed
Keith> until parse_and_eval is const, which I did not do. I thought that
Keith> might be a much more involved patch, and planned to do that
Keith> separately.
Ok, that's good enough for me.
Keith> That's all of them AFAICT. Anything further you want wrt to analyzing
Keith> callers that I missed?
Nope.
Tom
prev parent reply other threads:[~2013-03-11 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 0:12 Keith Seitz
2013-03-08 0:22 ` Pedro Alves
2013-03-08 1:02 ` Keith Seitz
2013-03-08 12:27 ` Pedro Alves
2013-03-08 13:55 ` Pedro Alves
2013-03-09 1:00 ` Pedro Alves
2013-03-09 1:04 ` Keith Seitz
2013-03-11 22:09 ` Keith Seitz
2013-03-12 10:18 ` Pedro Alves
2013-03-12 17:40 ` Keith Seitz
2013-03-08 14:54 ` Tom Tromey
2013-03-11 16:50 ` Keith Seitz
2013-03-11 18:30 ` Tom Tromey [this message]
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=87y5dtn61h.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--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