From: Tom Tromey <tromey@redhat.com>
To: Thomas Zander <zander@javalobby.org>
Cc: mauve-discuss@sources.redhat.com,
Jeff Sturm <jsturm@one-point.com>,
Michael Koch <konqueror@gmx.de>
Subject: Re: Eclipse and Classpath
Date: Fri, 30 Apr 2004 23:22:00 -0000 [thread overview]
Message-ID: <873c6lm57k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200404282354.50797.zander@javalobby.org>
>>>>> "Thomas" == Thomas Zander <zander@javalobby.org> writes:
Thomas> IIRC the biggest problem with using JUnit is that it depends
Thomas> of rather advanced JVM features; like reflection.
Yeah. However, Mauve already uses Class.forName and
Class.newInstance, so it is already relying on some reflection
capability.
Also, when Mauve was started, gcj limitations drove some of the design
decisions. In particular we set things up carefully to avoid
functionality we knew would not work with gcj. Since then things have
changed; all the free VMs are much more capable.
Tom
next prev parent reply other threads:[~2004-04-30 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0404241127510.5951-100000@ops2.one-point.com>
2004-04-28 20:02 ` Tom Tromey
2004-04-28 21:56 ` Thomas Zander
2004-04-30 23:22 ` Tom Tromey [this message]
[not found] <OFD30D19BA.CBC8235A-ON85256E84.007C2292-85256E84.007C73EC@us.ibm.com>
2004-04-28 22:54 ` Archie Cobbs
2004-04-29 5:09 ` C. Brian Jones
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=873c6lm57k.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=jsturm@one-point.com \
--cc=konqueror@gmx.de \
--cc=mauve-discuss@sources.redhat.com \
--cc=zander@javalobby.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).