From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/c++] migrate gcc_compiled to test_compiler_info
Date: Sun, 23 Nov 2003 19:24:00 -0000 [thread overview]
Message-ID: <20031123192452.71FE74B409@berman.michael-chastain.com> (raw)
ac> yea! draging around variables is a pain.
You could even do
proc test_compiler_info { compiler } {
global compiler_info
if { compiler_info == "uninitialized" } then {
get_compiler_info
}
if { compiler_info == "unknown" } then {
perror "I cannot figure out your compiler"
}
return ...;
}
But I'm not ready to put this on my TODO list today.
Michael C
next reply other threads:[~2003-11-23 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 19:24 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-23 18:20 Michael Elizabeth Chastain
2003-11-23 18:30 ` Andrew Cagney
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=20031123192452.71FE74B409@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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