Standardize the multiple-include protect.

[kopensolaris-gnu/glibc.git] / PROJECTS

diff --git a/PROJECTS b/PROJECTS
index b7272ee..f4cadfd 100644 (file)
--- a/PROJECTS
+++ b/PROJECTS
@@ -1,6 +1,6 @@
 Open jobs for finishing GNU libc:
 ---------------------------------
 Open jobs for finishing GNU libc:
 ---------------------------------

-Status: October 1996
+Status: April 1997

 
 If you have time and talent to take over any of the jobs below please
 contact <bug-glibc@prep.ai.mit.edu>
 
 If you have time and talent to take over any of the jobs below please
 contact <bug-glibc@prep.ai.mit.edu>


@@ -10,6 +10,8 @@ contact <bug-glibc@prep.ai.mit.edu>
 [ 1] Port to new platforms or test current version on formerly supported
      platforms.
 
 [ 1] Port to new platforms or test current version on formerly supported
      platforms.
 

+**** See http://www.gnu.org/software/libc/porting.html for more details.
+

 
 [ 2] Test compliance with standards.  If you have access to recent
      standards (IEEE, ISO, ANSI, X/Open, ...) and/or test suites you
 
 [ 2] Test compliance with standards.  If you have access to recent
      standards (IEEE, ISO, ANSI, X/Open, ...) and/or test suites you


@@ -17,7 +19,16 @@ contact <bug-glibc@prep.ai.mit.edu>
      standards if they do not contradict each other.
 
 
      standards if they do not contradict each other.
 
 

-[ 3] Write translations for the GNU libc message for the so far
+[ 3] The IMHO opinion most important task is to write a more complete
+     test suite.  We cannot get too many people working on this.  It is
+     not difficult to write a test, find a definition of the function
+     which I normally can provide, if necessary, and start writing tests
+     to test for compliance.  Beside this, take a look at the sources
+     and write tests which in total test as many paths of execution as
+     possible.
+
+
+[ 4] Write translations for the GNU libc message for the so far

      unsupported languages.  GNU libc is fully internationalized and
      users can immediately benefit from this.
 
      unsupported languages.  GNU libc is fully internationalized and
      users can immediately benefit from this.
 


@@ -26,13 +37,15 @@ contact <bug-glibc@prep.ai.mit.edu>
      for the current status (of course better use a mirror of prep).
 
 
      for the current status (of course better use a mirror of prep).
 
 

-[ 4] Write wordexp() function; this is described in POSIX.2, the
+[ 5] Write wordexp() function; this is described in POSIX.2, the

      header <wordexp.h> already exists.
 
      Implementation idea: use some functions from bash.
 
      header <wordexp.h> already exists.
 
      Implementation idea: use some functions from bash.
 

+**** Somebody is working on this.  Help may or may not be appreciated.

 
 

-[ 5] Write `long double' versions of the math functions.  This should be
+
+[ 6] Write `long double' versions of the math functions.  This should be

      done in collaboration with the NetBSD and FreeBSD people.
 
      The libm is in fact fdlibm (not the same as in Linux libc).
      done in collaboration with the NetBSD and FreeBSD people.
 
      The libm is in fact fdlibm (not the same as in Linux libc).


@@ -41,7 +54,18 @@ contact <bug-glibc@prep.ai.mit.edu>
      the rest.
 
 
      the rest.
 
 

-[ 6] If you enjoy assembler programming (as I do --drepper :-) you might
+[ 7] Several math functions have to be written:
+
+     - exp2
+
+     each with float, double, and long double arguments.
+
+     Beside this most of the complex math functions which are new in
+     ISO C 9X should be improved.  Writing some of them in assembler is
+     useful to exploit the parallelism which often is available.
+
+
+[ 8] If you enjoy assembler programming (as I do --drepper :-) you might

      be interested in writing optimized versions for some functions.
      Especially the string handling functions can be optimized a lot.
 
      be interested in writing optimized versions for some functions.
      Especially the string handling functions can be optimized a lot.
 


@@ -56,32 +80,38 @@ contact <bug-glibc@prep.ai.mit.edu>
      work.
 
 
      work.
 
 

-[ 7] Write nftw() function.  Perhaps it might be good to reimplement the
-     ftw() function as well to share most of the code.
-
-**** Almost done!
-
-
-[ 8] Write AVL-tree based tsearch() et.al. functions.  Currently only
-     a very simple algorithm is used.
-     There is a public domain version but using this would cause problems
-     with the assignment.
-
-
-[ 9] Extend regex and/or rx to work with wide characters and complete
+[10] Extend regex and/or rx to work with wide characters and complete

      implementation of character class and collation class handling.
 
      It is planed to do a complete rewrite.
 
 
      implementation of character class and collation class handling.
 
      It is planed to do a complete rewrite.
 
 

-[10] Write access function for netmasks, bootparams, and automount
+[11] Write access function for netmasks, bootparams, and automount

      databases for nss_files and nss_db module.
      The functions should be embedded in the nss scheme.  This is not
      hard and not all services must be supported at once.
 
 
      databases for nss_files and nss_db module.
      The functions should be embedded in the nss scheme.  This is not
      hard and not all services must be supported at once.
 
 

-[11] Rewrite utmp/wtmp functions to use database functions.  This is much
-     better than the normal flat file format.
+[13] Several more or less small functions have to be written:
+
+     + tcgetid() and waitid()                  from XPG4.2
+     + grantpt(), ptsname(), unlockpt()                from XPG4.2
+
+     More information is available on request.
+
+
+[14] We need to write a library for on-the-fly transformation of streams
+     of text.  In fact, this would be a recode-library (you know, GNU recode).
+     This is needed in several places in the GNU libc and I already have
+     rather concrete plans but so far no possibility to start this.
+
+
+[15] Cleaning up the header files.  Ideally, each header style should
+     follow the "good examples".  Each variable and function should have
+     a short description of the function and its parameters.  The prototypes
+     should always contain variable names which can help to identify their
+     meaning; better than
+
+               int foo __P ((int, int, int, int));

 
 

-     Please contact bug-glibc@prep.ai.mit.edu before starting to avoid
-     duplicated work.
+     Blargh!