From: Tom Tromey <tromey@redhat.com>
To: Java Patch List <java-patches@gcc.gnu.org>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Patch: FYI: status update
Date: Sun, 03 Nov 2002 14:03:00 -0000 [thread overview]
Message-ID: <87vg3emi4m.fsf@fleche.redhat.com> (raw)
I'm checking this in.
This updates the status page:
* Adds missing info
* Updates package info
* Links to a couple useful comparison pages
Tom
Index: htdocs/java/ChangeLog
from Tom Tromey <tromey@redhat.com>
* status.html: Wrapped paragraph in <p>. Mention some programs we
provide.
(java.nio, javax.naming, javax.transaction, java.text): Updated.
Link to comparison pages.
Index: htdocs/java/status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/status.html,v
retrieving revision 1.18
diff -u -r1.18 status.html
--- htdocs/java/status.html 2 Nov 2002 14:33:59 -0000 1.18
+++ htdocs/java/status.html 3 Nov 2002 22:03:09 -0000
@@ -14,9 +14,9 @@
<h1>GCJ Status</h1>
-Status of GCJ as of the current release (gcc 3.2).
+<p>Status of GCJ as of the current release (gcc 3.2).
Improvements that are only in the CVS repository, but not
-in gcc 3.2 are marked as "in CVS".
+in gcc 3.2 are marked as "in CVS".</p>
<table id="features" border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
@@ -39,6 +39,7 @@
native) and run-time (loading classes). Both miss some tests, and
you should not (yet) rely on their correctness for security.</li>
<li>A "conservative" garbage collector.</li>
+<li>A replacement for the jar, javah, rmic, and rmiregistry programs.</li>
<li>An extensive class library - see below.</li>
</ul>
@@ -71,7 +72,7 @@
<dt class="package">java.net</dt>
<dd>Ok.</dd>
<dt class="package">java.nio</dt>
-<dd>Ok.</dd>
+<dd>Some code; not working.</dd>
<dt class="package">java.rmi</dt>
<dd>Ok.</dd>
<dt class="package">java.security</dt>
@@ -87,18 +88,28 @@
<dt class="package">java.util.zip</dt>
<dd>Ok.</dd>
<dt class="package">java.text</dt>
-<dd>Ok.</dd>
+<dd>Ok, but most localization data not available.</dd>
<dt class="package">javax.accessibility</dt>
<dd>Some code; status unknown.</dd>
<dt class="package">javax.naming</dt>
-<dd>Some code; status unknown.</dd>
+<dd>Complete, but no providers written.</dd>
<dt class="package">javax.sql</dt>
<dd>Some code; status unknown.</dd>
<dt class="package">javax.swing</dt>
<dd>Some code, but not enough for real applications.</dd>
<dt class="package">javax.transaction</dt>
-<dd>Some code; status unknown.</dd>
+<dd>Complete, but no providers written.</dd>
</dl>
+
+<p>You can see <a
+href="http://gcc.gnu.org/java/libgcj-classpath-compare.html">a
+comparison of our classes with Classpath's</a>. Differences here are
+merged from time to time.</p>
+
+<p>You can also see <a
+href="ftp://alpha.gnu.org/pub/gnu/classpath/nightly/tests/classpath-jdk13-compare.txt">a
+comparison of Classpath with the JDK</a>. This is roughly equivalent
+to a comparison of libgcj with the JDK.</p>
<table id="targets" border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">
reply other threads:[~2002-11-03 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87vg3emi4m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.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).