/[classpath]/classpath/TODO
ViewVC logotype

Diff of /classpath/TODO

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.6 by cbj, Tue Dec 24 05:35:22 2002 UTC revision 1.7 by cbj, Sat Feb 15 15:08:08 2003 UTC
# Line 1  Line 1 
1  The Classpath TODO list as of 2002/05/05  The Classpath TODO list as of 2002/05/05
2    
3  -- Modify Classpath build to support libgcj out of the box.  Ideally  -- Write Mauve (http://sourceware.cygnus.com/mauve/) tests for those
4     the gcj folks could simply include a stock classpath in one of their     classes that don't have them.
5     distribution subdirectories, have their master configure run a configure  
6     on Classpath the appropriate arguments, and everything would build.  -- Write Java 2 packages not currently included or improve existing
7       ones.
8    
9  -- Modify ClassLoader.getSystemResource() to support loading classes  -- Modify ClassLoader.getSystemResource() to support loading classes
10     from zip files in the CLASSPATH.  This requires java.util.zip to     from zip files in the CLASSPATH.  This requires java.util.zip to
11     be integrated first.  Jar filed can probably be treated as zip     be integrated first.  Jar files can probably be treated as zip
12     files for now.     files for now.
13    
14  -- Continue comparison and merge of classes between Classpath and GCJ.  -- Continue comparison and merge of classes between Classpath and GCJ.
# Line 27  The Classpath TODO list as of 2002/05/05 Line 28  The Classpath TODO list as of 2002/05/05
28  -- Update the GNU Classpath Hacker's Guide.  There is a master texinfo  -- Update the GNU Classpath Hacker's Guide.  There is a master texinfo
29     file in the doc/ directory in Classpath CVS.     file in the doc/ directory in Classpath CVS.
30    
 -- 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.  
   
31  -- Audit the code to identify methods that do not have Javadoc comments  -- Audit the code to identify methods that do not have Javadoc comments
32     and/or comments that are incomplete.  All input parameters, return     and/or comments that are incomplete.  All input parameters, return
33     values, etc should be documentes.  Also look for Javadoc comments on     values, etc should be documentes.  Also look for Javadoc comments on
# Line 64  The Classpath TODO list as of 2002/05/05 Line 59  The Classpath TODO list as of 2002/05/05
59     JDK 1.1 version.  You can obtain that variable value using the     JDK 1.1 version.  You can obtain that variable value using the
60     serialver command.     serialver command.
61    
62  -- Do real life serialization compatibility tests of our code with Kaffe  -- Do real life serialization compatibility tests of our code vs
63     and the JDK.     the JDK using serialcompat from Japitools.
64    
65  -- Audit code for thread safety.  -- Audit code for thread safety.
66    
67  -- Update the packaging of Classpath to make sure that we can build  -- Audit Java code for proper Security implementation.
68     good distribution tarballs.  
69    -- Audit native code for security, memory handling, etc.
70    
71  -- Bug reports are always welcome.  They are double welcome if they  -- Bug reports are always welcome.  They are double welcome if they
72     are accompanied by a Mauve test that reproduces the bug.     are accompanied by a Mauve test that reproduces the bug.

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26