1 |
The Classpath TODO list as of 2000/04/17 |
The Classpath TODO list as of 2001/11/03 |
2 |
|
|
3 |
-- Modify Classpath build to support libgcj out of the box. Ideally |
-- Modify Classpath build to support libgcj out of the box. Ideally |
4 |
the gcj folks could simply include a stock classpath in one of their |
the gcj folks could simply include a stock classpath in one of their |
5 |
distribution subdirectories, have their master configure run a configure |
distribution subdirectories, have their master configure run a configure |
6 |
on Classpath the appropriate arguments, and everything would build. |
on Classpath the appropriate arguments, and everything would build. |
7 |
|
|
|
-- Integrate packages from libgcj that don't exist in Classpath: |
|
|
o java.util.zip |
|
|
o java.util.jar |
|
|
|
|
8 |
-- Modify ClassLoader.getSystemResource() to support loading classes |
-- Modify ClassLoader.getSystemResource() to support loading classes |
9 |
from zip files in the CLASSPATH. This requires java.util.zip to |
from zip files in the CLASSPATH. This requires java.util.zip to |
10 |
be integrated first. Jar filed can probably be treated as zip |
be integrated first. Jar filed can probably be treated as zip |
11 |
files for now. |
files for now. |
12 |
|
|
13 |
-- Perform a class by class comparison in packages where both Classpath |
-- Continue comparison and merge of classes between Classpath and GCJ. |
14 |
and libgcj have implementations, and make recommendations for how |
|
15 |
to merge them and/or which implementations are superior. This has |
Current status: http://gcc.gnu.org/java/libgcj-classpath-compare.html |
|
been done for java.net by Gaute Smaaland. See the mail message: |
|
|
|
|
|
http://www.mail-archive.com/classpath@gnu.org/msg02135.html |
|
|
|
|
|
for his comments. The packages where we need similar work are: |
|
|
o java.io |
|
|
o java.lang |
|
|
o java.lang.reflect |
|
|
o java.text |
|
|
o java.security |
|
16 |
|
|
17 |
Please keep in mind that Cygnus wishes to continue to use CNI |
Please keep in mind that Cygnus wishes to continue to use CNI |
18 |
as their preferred native interface. See: |
as their preferred native interface. See: |
19 |
|
|
20 |
http://sourceware.cygnus.com/java/papers/cni/t1.html |
http://sourceware.cygnus.com/java/papers/cni/t1.html |
21 |
|
|
22 |
-- Identify a way to resolve the CNI versus JNI issue. JNI is the |
-- No resolution was identified for generating JNI compatible code from |
23 |
Java standard for calling native methods. Classpath needs to support |
CNI source. The simple solution has been adopted to include |
24 |
this for standards compliance. CNI is the Cygnus Native Interface, |
both in GNU Classpath. Provisions for compiling CNI correctly need |
25 |
an efficient method for calling native code, but one limited to use |
to be implemented. |
|
with gcj. Cygnus wishes to continue using this because it is more |
|
|
efficient than JNI in their implementation, and uses substantially |
|
|
easier and more readable native code. Proposed solutions to date: |
|
|
o Binary interface |
|
|
o A .in file that is pre-processed through a script to generate |
|
|
CNI or JNI as desired. |
|
|
o Multiple implementations with a compile time switch. |
|
|
o Pre-processing script to convert CNI source to JNI |
|
|
|
|
|
-- New web site. The Classpath web site at: |
|
|
|
|
|
http://www.classpath.org/ |
|
|
|
|
|
is hideously out of date. Please contact Paul Fisher (rao@gnu.org) |
|
|
and Brian Jones (cbj@gnu.org) if you wish to work in this. |
|
26 |
|
|
27 |
-- Update the GNU Classpath Hacker's Guide. There is a master texinfo |
-- Update the GNU Classpath Hacker's Guide. There is a master texinfo |
28 |
file in the doc/ directory in Classpath CVS. |
file in the doc/ directory in Classpath CVS. |
29 |
|
|
|
-- Implement a bug tracking system for Classpath. |
|
|
|
|
30 |
-- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those |
-- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those |
31 |
classes that don't have them. |
classes that don't have them. |
32 |
|
|
43 |
|
|
44 |
-- java.awt: Mostly done and compiles cleanly. A few classes are |
-- java.awt: Mostly done and compiles cleanly. A few classes are |
45 |
missing. Needs to be debugged and integrated with Paul Fisher's |
missing. Needs to be debugged and integrated with Paul Fisher's |
46 |
AWT peers. This task should not be worked on for the time being. |
AWT peers. |
47 |
|
|
48 |
-- java.awt.datatransfer: Coded and compiles cleanly. Needs |
-- java.awt.datatransfer: Coded and compiles cleanly. Needs |
49 |
debugging. This task should be considered "On Hold" for now. |
debugging. This task should be considered "On Hold" for now. |
51 |
-- java.awt.event: Coded and compiles cleanly. Needs debugging. |
-- java.awt.event: Coded and compiles cleanly. Needs debugging. |
52 |
This task should be considered "On Hold" for now. |
This task should be considered "On Hold" for now. |
53 |
|
|
54 |
-- java.awt.image: Unsure of status but partially implemented. |
-- java.awt.image: Partially implemented, could use help with identifying |
55 |
|
the proper image manipulation algorithms that need to be implemented. |
56 |
|
|
57 |
-- java.awt.peer: Done. Nothing needs to be done here. |
-- java.awt.peer: Done. Nothing needs to be done here. |
58 |
|
|
63 |
|
|
64 |
-- java.lang: Needs to be merged with libgcj. See above. |
-- java.lang: Needs to be merged with libgcj. See above. |
65 |
|
|
66 |
-- java.math: Needs to be merged with libgcj. See above. Missing |
-- java.math: Done. |
|
some methods. |
|
67 |
|
|
68 |
-- java.net: Merger with libgcj in progress. No tasks to be done at |
-- java.net: Needs to be merged with libgcj. See above. |
|
this time. |
|
69 |
|
|
70 |
-- java.rmi: No implementation. Rumor has it that Transvirtual (Kaffe) |
-- java.rmi: Done. |
|
is producing a version we can use. |
|
71 |
|
|
72 |
-- java.security: Debug the implementation and get it working with Japhar |
-- java.security: Debug the implementation. |
|
and/or gcj. Mark Benvenuto (mcb54@columbia.edu) wrote this, but |
|
|
I'm not sure that it is totally running. |
|
73 |
|
|
74 |
-- java.sql: Coded and compiles cleanly. Needs debugging. |
-- java.sql: Needs debugging. |
75 |
|
|
76 |
-- java.text: Needs to be merged with libgcj. See above. |
-- java.text: Needs to be merged with libgcj. See above. |
77 |
|
|
78 |
-- java.util: Needs to be merged with libgcj. See above |
-- java.util: Needs to be merged with libgcj. See above |
79 |
|
|
80 |
-- java.util.zip: Need to merge in the libgcj version. See above. |
-- java.util.zip: Need to be merged with libgcj. See above. |
81 |
|
|
82 |
------------------------------------------------------------------------- |
------------------------------------------------------------------------- |
83 |
|
|
84 |
-- Write Java 1.2 packages not currently included or improve existing |
-- Write Java 1.2 packages not currently included or improve existing |
85 |
ones. |
ones. |
86 |
|
|
|
-- Write an implementation of Swing. This is a big job and should |
|
|
probably be a separate, non-Classpath project that can be shared |
|
|
with Kaffe. Please write to the mailing list if you are interested |
|
|
in helping with this. (classpath@gnu.org) |
|
|
|
|
87 |
-- Figure out an easy method of generating online Javadocs from our |
-- Figure out an easy method of generating online Javadocs from our |
88 |
code. This will probably involve lots of misc HTML fixes. |
code. This will probably involve lots of misc HTML fixes. |
89 |
|
|
90 |
-- Audit the code to identify methods that do not have Javadoc comments |
-- Audit the code to identify methods that do not have Javadoc comments |
91 |
and/or comments that are incomplete. All input parameters, return |
and/or comments that are incomplete. All input parameters, return |
92 |
values, etc should be documentes. Also look for Javadoc comments on |
values, etc should be documentes. Also look for Javadoc comments on |
93 |
variables that are serializable. See http://java.sun.com/j2se/javadoc/writingdoccomments/index.html#tag |
variables that are serializable. |
94 |
|
See http://java.sun.com/j2se/javadoc/writingdoccomments/index.html#tag |
95 |
for details of what should be where in comments. |
for details of what should be where in comments. |
96 |
|
|
97 |
-- Figure out a way to generate a hardcopy manual for the Java class |
-- Figure out a way to generate a hardcopy manual for the Java class |