Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfc] Revamp logical.exp
Date: Wed, 14 Jul 2004 18:20:00 -0000	[thread overview]
Message-ID: <20040714182014.4F59C4B104@berman.michael-chastain.com> (raw)

The basic idea and the implementation are good.

I hand-checked all the data in the tables for correctness.
It all looks fine to me.

In the test name, could you include something grep'able.
So that if someone gets:

  FAIL: logical.exp: evaluation of x == y, {x = 1, y = 0}

They can find the right gdb_test by grepping on the wordage
("evalation of").

Yes, I see that there are only two gdb_test's in the whole file,
but I like the test names to have searchable parts.  This has
been essential to me when finding things in structs.exp.

Also please consider adding $val into the test name:

  FAIL: logical.exp: evaluation of x == y; {x = 1, y = 0}; expected 0

I think that makes it easier to see whether the test is written
correctly or not, especially when someone goes to add 50 new tests.

And, as always ... did you run it somewhere?

Michael C

2004-07-14  Andrew Cagney  <cagney@gnu.org>

	* gdb.base/logical.exp: Update copyright.
	(evaluate): New procedure.  Use to re-implement tests using
	several tables.


             reply	other threads:[~2004-07-14 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 18:20 Michael Elizabeth Chastain [this message]
2004-07-14 19:15 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-07-14 20:34 Michael Elizabeth Chastain
2004-07-15 17:40 ` Andrew Cagney
2004-07-14 16:38 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=20040714182014.4F59C4B104@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