From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>,
david@streamline-computing.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] PR gdb/648 (eval.c approval reqd)
Date: Mon, 30 Aug 2004 14:17:00 -0000 [thread overview]
Message-ID: <4133368C.7020504@gnu.org> (raw)
In-Reply-To: <412F5E39.nailASJ1Y0VWN@mindspring.com>
> Andrew Cagney <cagney@gnu.org> wrote:
>
>>> proc deprecated_compile_with_gnu_fortran { program } { .... }
>
>
> Ewww.
*2 :-)
> But you do have a lot of experience in gdb balancing feature additions
> with infrastructure cleanup, so I have to give some weight to that.
>
> So, okay. If you, or somebody, wants to do that, go for it.
>
> . put it in a new file, lib/fortran-support.exp.
> . the deprecated_* name is a nice touch.
David, this makes the testcase possible, can that be added.
Andrew
next prev parent reply other threads:[~2004-08-30 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 22:10 [PATCH/RFA] PR gdb/648 David Lecomber
2004-08-13 10:25 ` David Lecomber
2004-08-13 10:32 ` Michael Chastain
2004-08-13 22:14 ` Jim Blandy
2004-08-16 12:33 ` David Lecomber
2004-08-16 12:38 ` David Lecomber
2004-08-18 16:36 ` Jim Blandy
2004-08-20 13:37 ` [PATCH/RFA] PR gdb/648 (eval.c approval reqd) David Lecomber
2004-08-20 13:45 ` David Lecomber
2004-08-25 5:53 ` Jim Blandy
2004-08-25 7:24 ` David Lecomber
2004-08-27 0:00 ` Jim Blandy
2004-08-27 9:15 ` David Lecomber
2004-08-27 13:52 ` Andrew Cagney
2004-08-27 13:58 ` Michael Chastain
2004-08-27 14:14 ` Andrew Cagney
2004-08-27 14:57 ` Michael Chastain
2004-08-27 15:57 ` Andrew Cagney
2004-08-27 16:15 ` Michael Chastain
2004-08-30 14:17 ` Andrew Cagney [this message]
2004-08-23 19:26 ` [PATCH/RFA] PR gdb/648 Andrew Cagney
2004-08-24 18:03 ` Jim Blandy
2004-08-15 8:19 ` Michael Chastain
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=4133368C.7020504@gnu.org \
--to=cagney@gnu.org \
--cc=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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