From: Michael Elizabeth Chastain <mec@shout.net>
To: bkoz@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ testsuite 1.3: member_data_static.exp (resend)
Date: Wed, 29 May 2002 08:34:00 -0000 [thread overview]
Message-ID: <200205291533.g4TFXvp21576@duracef.shout.net> (raw)
> template class __gnu_test::gnu_obj_3<long>;
> template class __gnu_test::gnu_obj_2<int>;
I'm happy with this. It's better than my "refer" kludge.
I'll try this out on the next iteration, which will be in a day or two
(my test bed is busy right now).
Michael C
next reply other threads:[~2002-05-29 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 8:34 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 12:29 Michael Elizabeth Chastain
2002-05-30 12:12 Michael Elizabeth Chastain
2002-05-28 15:26 Michael Elizabeth Chastain
2002-05-29 8:09 ` Benjamin Kosnik
2002-05-29 8:19 ` Daniel Jacobowitz
2002-05-29 8:34 ` B. Kosnik
2002-05-29 9:39 ` Daniel Jacobowitz
2002-05-30 7:56 ` Benjamin Kosnik
2002-05-27 16:02 Michael Elizabeth Chastain
2002-05-28 9:17 ` Benjamin Kosnik
2002-05-28 9:47 ` Daniel Jacobowitz
2002-05-27 6:28 Benjamin Kosnik
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=200205291533.g4TFXvp21576@duracef.shout.net \
--to=mec@shout.net \
--cc=bkoz@redhat.com \
--cc=drow@mvista.com \
--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