From: Tom Tromey <tromey@cygnus.com>
To: Artur Biesiadowski <abies@pg.gda.pl>
Cc: mauve <mauve-discuss@sourceware.cygnus.com>
Subject: Re: BitSet patch
Date: Sun, 21 Mar 1999 10:00:00 -0000 [thread overview]
Message-ID: <8790cq3epw.fsf@cygnus.com> (raw)
In-Reply-To: Artur Biesiadowski's message of Sun, 21 Mar 1999 16:54:47 +0100
>>>>> "Artur" == Artur Biesiadowski <abies@pg.gda.pl> writes:
Artur> A bit better test now - it was possible for and() to just clear
Artur> a bitset and pass the test.
I checked this in.
Artur> BTW it is quite hard to write a good test without 'mutation
Artur> testing' - introducing explicit errors in tested code :)
Yeah.
Sometimes I add new test cases to test for specific bugs I find in my
code. I encourage everybody to do this. There's some chance that
different programmers will make similar mistakes.
Tom
WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@cygnus.com>
To: Artur Biesiadowski <abies@pg.gda.pl>
Cc: mauve <mauve-discuss@sourceware.cygnus.com>
Subject: Re: BitSet patch
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <8790cq3epw.fsf@cygnus.com> (raw)
Message-ID: <19990401000000.QrnIgnz6D9-W1v7sYLk1DiXNeJAgLbSjh96FLqu5xhY@z> (raw)
In-Reply-To: <36F51647.BC88D163@pg.gda.pl>
>>>>> "Artur" == Artur Biesiadowski <abies@pg.gda.pl> writes:
Artur> A bit better test now - it was possible for and() to just clear
Artur> a bitset and pass the test.
I checked this in.
Artur> BTW it is quite hard to write a good test without 'mutation
Artur> testing' - introducing explicit errors in tested code :)
Yeah.
Sometimes I add new test cases to test for specific bugs I find in my
code. I encourage everybody to do this. There's some chance that
different programmers will make similar mistakes.
Tom
next prev parent reply other threads:[~1999-03-21 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-21 9:46 Artur Biesiadowski
1999-03-21 10:00 ` Tom Tromey [this message]
1999-04-01 0:00 ` Tom Tromey
1999-04-01 0:00 ` Artur Biesiadowski
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=8790cq3epw.fsf@cygnus.com \
--to=tromey@cygnus.com \
--cc=abies@pg.gda.pl \
--cc=mauve-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).