From: Mark Wielaard <mark@klomp.org>
To: Audrius Meskauskas <audriusa@bluewin.ch>
Cc: mauve-discuss@sourceware.org, Roman Kennke <kennke@aicas.com>
Subject: Re: junit.framework.Assert
Date: Wed, 27 Dec 2006 15:32:00 -0000 [thread overview]
Message-ID: <1167233505.11559.10.camel@localhost.localdomain> (raw)
In-Reply-To: <4590364F.6020503@bluewin.ch>
Hi Audrius,
On Mon, 2006-12-25 at 21:36 +0100, Audrius Meskauskas wrote:
> Today I have discovered that junit.framework.Assert seems not
> compileable, because it twice calls the non existing methods of the
> TestHarness:
> check(double, double, double).
>
> It seems trivial to implement the workaround. Should we fix this?
Yes, please. I just noticed this today. I assume this class isn't
compiled in the default Makefile/Harness implementation. But it is bad
to have non-compilable classes in the tree (makes some IDEs like Eclipse
really unhappy).
Cheers,
Mark
next prev parent reply other threads:[~2006-12-27 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 20:36 junit.framework.Assert Audrius Meskauskas
2006-12-27 15:32 ` Mark Wielaard [this message]
2006-12-28 15:39 ` junit.framework.Assert Roman Kennke
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=1167233505.11559.10.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=audriusa@bluewin.ch \
--cc=kennke@aicas.com \
--cc=mauve-discuss@sourceware.org \
/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).