From: Tom Tromey <tromey@redhat.com>
To: Peter Naulls <peter@erble.freeserve.co.uk>
Cc: mauve-discuss@sourceware.cygnus.com
Subject: Re: Bytecode verifiers
Date: Wed, 20 Dec 2000 09:51:00 -0000 [thread overview]
Message-ID: <877l4vynkr.fsf@creche.redhat.com> (raw)
In-Reply-To: <e73adc2f4a%peter@erble.freeserve.co.uk>
>>>>> "Peter" == Peter Naulls <peter@erble.freeserve.co.uk> writes:
Peter> One of the problems here is that Mauve is really only a test of
Peter> the library implementation - it doesn't (but perhaps should)
Peter> target weak spots in JVMs; it's not really organised in a
Peter> manner suitable for this - the tests are arranged in terms of
Peter> library functionality, not JVM functionality.
For the completeness issue the only thing to do is for people to write
more tests. Feel free to contribute!
For JVM tests, we could easily add a new directory for these. We
could even add an entirely new test harness just for JVM tests, if
that is necessary. We aren't overly constrained by the current way of
doing things. Contributions welcome...
Tom
next prev parent reply other threads:[~2000-12-20 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 3:08 Bernard Serpette
2000-12-20 4:49 ` Peter Naulls
2000-12-20 9:51 ` Tom Tromey [this message]
2000-12-20 15:01 ` Peter Naulls
2000-12-21 21:48 ` tests that pass but indicate an error? Brian Jones
2000-12-21 22:11 ` Tom Tromey
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=877l4vynkr.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=mauve-discuss@sourceware.cygnus.com \
--cc=peter@erble.freeserve.co.uk \
/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).