From: "Anthony Green" <email@example.com>
To: Torsten RÃÂ¼ger <firstname.lastname@example.org>
Cc: <email@example.com>, <firstname.lastname@example.org>
Subject: Re: PostgreSQL jdbc drivers + gcj
Date: Wed, 10 Oct 2001 01:23:00 -0000 [thread overview]
Message-ID: <email@example.com> (raw)
> Are you saying this all works. I mean it's tested, doesn't just compile ?
> That would be great news, because we're using a fair few of those, and I
> was just about to test.
I think most of these work pretty well. For tomcat, servlets work but JSP
pages don't right now. That will take a little hacking of the tomcat code
because there are too many built in assumptions about the compiler generating
.class files, etc.
I feel somewhat confident about xerces, xalan, bsf, rhino, pgsql-jdbc, bcel,
cup and the regexp packages (which have test suites). Actually, xalan uses
many of these (xerces, bsf, rhino, bcel, cup), and it appears to work pretty
well. Much of the Bouncy Castle JCE stuff passes its testsuite. I expect the
failures are bugs in our library code (BigInteger, or SecureRandom, or ???).
The next major project is to hook all of the various testsuites into "make
check". It currently builds verious test programs with "make check", but I'd
like them to actually be run and have their results checked. I don't know if
I'll be able to do this any time soon, so help is appreciated!
Be aware that you'll need the very latest development version of GCC (from
CVS) in order build and run this stuff.
next prev parent reply other threads:[~2001-10-10 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 23:32 Anthony Green
[not found] ` <3BC3F52F.firstname.lastname@example.org>
2001-10-10 1:23 ` Anthony Green [this message]
2001-10-10 9:43 ` Alexandre Petit-Bianco
2001-10-29 4:36 ` WebMacro and Jetty Torsten RÃ¼ger
2001-10-30 13:54 ` Anthony Green
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).