summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorBrian Jones <cbj@gnu.org>2003-02-15 15:08:08 +0000
committerBrian Jones <cbj@gnu.org>2003-02-15 15:08:08 +0000
commit4171e763104e2f7ecf2df719a723320c36c9313f (patch)
tree7366fcddb45df1a1854e4452bf89797ceaee0e3b /TODO
parent7417a5f627cec7310285ed4598a838ee70a4267e (diff)
downloadclasspath-4171e763104e2f7ecf2df719a723320c36c9313f.tar.gz
2003-02-15 Julian Dolby <dolby@us.ibm.com>
* configure.in (portable-native-sync): new configure option allows user to configure native AWT peers to use Java threading primitives instead of pthread primitives. * native/jni/gtk-peer/gnu_java_awt_peer_gtk_GtkMainThread.c (Java_gnu_java_awt_peer_gtk_GtkMainThread_gtkInit): get JavaVM reference before calling g_thread_init if using PORTABLE_NATIVE_SYNC * native/jni/gtk-peer/gthread-jni.c (maybe_rethrow): utility method checks for JNI exception and throws another exception (maybe it should clear the previous first?) (allocatePlainObject): new method used to create a mutex (freePlainObject): new method use to free a mutex (takeLock): new method (releaseLock): new method (g_mutex_new_jni_impl): uses allocatePlainObject instead (g_mutex_lock_jni_impl): uses takeLock instead (g_mutex_unlock_jni_impl): uses releaseLock instead (g_mutex_free_jni_impl): uses freePlainObject instead (g_private_new_jni_impl): implemented (g_private_get_jni_impl): implemented (g_private_set_jni_impl): implemented (g_cond_new_jni_impl): implemented; uses allocatePlainObject (g_cond_signal_jni_impl): implemented (g_cond_broadcast_jni_impl): implemented (g_cond_wait_jni_impl): implemented (g_cond_timed_wait_jni_impl): implemented (g_cond_free_jni_impl): implemented; uses freePlainObject * native/jni/gtk-peer/gthread-jni.h: extern JavaVM *gdk_vm 2003-02-15 C. Brian Jones <cbj@gnu.org> * TODO: updated
Diffstat (limited to 'TODO')
-rw-r--r--TODO26
1 files changed, 11 insertions, 15 deletions
diff --git a/TODO b/TODO
index 67af46717..f0ac23906 100644
--- a/TODO
+++ b/TODO
@@ -1,13 +1,14 @@
The Classpath TODO list as of 2002/05/05
--- Modify Classpath build to support libgcj out of the box. Ideally
- the gcj folks could simply include a stock classpath in one of their
- distribution subdirectories, have their master configure run a configure
- on Classpath the appropriate arguments, and everything would build.
+-- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those
+ classes that don't have them.
+
+-- Write Java 2 packages not currently included or improve existing
+ ones.
-- Modify ClassLoader.getSystemResource() to support loading classes
from zip files in the CLASSPATH. This requires java.util.zip to
- be integrated first. Jar filed can probably be treated as zip
+ be integrated first. Jar files can probably be treated as zip
files for now.
-- Continue comparison and merge of classes between Classpath and GCJ.
@@ -27,12 +28,6 @@ The Classpath TODO list as of 2002/05/05
-- Update the GNU Classpath Hacker's Guide. There is a master texinfo
file in the doc/ directory in Classpath CVS.
--- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those
- classes that don't have them.
-
--- Write Java 2 packages not currently included or improve existing
- ones.
-
-- Audit the code to identify methods that do not have Javadoc comments
and/or comments that are incomplete. All input parameters, return
values, etc should be documentes. Also look for Javadoc comments on
@@ -64,13 +59,14 @@ The Classpath TODO list as of 2002/05/05
JDK 1.1 version. You can obtain that variable value using the
serialver command.
--- Do real life serialization compatibility tests of our code with Kaffe
- and the JDK.
+-- Do real life serialization compatibility tests of our code vs
+ the JDK using serialcompat from Japitools.
-- Audit code for thread safety.
--- Update the packaging of Classpath to make sure that we can build
- good distribution tarballs.
+-- Audit Java code for proper Security implementation.
+
+-- Audit native code for security, memory handling, etc.
-- Bug reports are always welcome. They are double welcome if they
are accompanied by a Mauve test that reproduces the bug.