From: Fernando Nasser <fnasser@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] MI varobj testsuite support
Date: Fri, 18 Oct 2002 09:49:00 -0000 [thread overview]
Message-ID: <3DB03B3E.1020208@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210171336590.10038-100000@valrhona.uglyboxes.com>
Keith Seitz wrote:
> It's only a convenience. I find it easier to write "Varobj::create foo"
> than "-var-create foo * foo"; I can never remember the whole syntax
> without looking it up.
>
I am concerned with the legibility of the tests and when people may be
reproducing parts of it by hand. The "-var-create foo * foo" is better
for that.
The other commands generate a very simple output that is easy to create
an pattern for and it is also easier for human interpretation (same
situation as above).
The "pattern" part is cool though. Why don't you submit just that for
now?
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
prev parent reply other threads:[~2002-10-18 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 9:26 Keith Seitz
2002-10-17 13:22 ` Fernando Nasser
2002-10-17 13:38 ` Keith Seitz
2002-10-18 9:49 ` Fernando Nasser [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=3DB03B3E.1020208@redhat.com \
--to=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=keiths@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