Main Todo Items===============We are looking for volunteers to do the following tasks.Consult the TODO files in each directory first for specificrequirements.* 1st-line support on the mailing lists (e.g. checking that bugs arereproducible, and that all relevant information is supplied)* Modified Ei(x) function (see specfunc/TODO)* Eigensystems for non-symmetric matrices* Quasi-random number distributions * ODE algorithms from RKSUITE* Incomplete Fermi-Dirac functions* General Legendre functions* Spheroidal wave functions* Weierstrass elliptic functions* Complex Bessel Functions* Additional volunteers with access to a good library to get copies ofpapers for other developers.* Estimates of condition numbers for linear solvers* Sine and Cosine Transforms from FFTPACK  (Alok Singhal <as8ca@virginia.edu>)* Cubature, e.g as provided by Cubpack. (Gert Van den Eynde<gvdeynde@sckcen.be> ?)* Mathieu functions (Lowell Johnson <ldj00@sio.midco.net>)* Fresnel Integrals ("Juergen J. Zach" <jjzach@pacific.mps.ohio-state.edu>)* Cumulative Distribution functions for discrete random distributionsOther tasks:* Remove use of long double internally, e.g. as an accumulator inloops. It introduces variation between platforms which is undesirable.It should be replaced with a preprocessor variable ACC_DOUBLE sothat the user can compile the library with the old long doublebehavior if desired.* Use BLAS internally as much as possible, to take advantage of speed improvements on large-scale systems.  There may be someinstances where a simple for() loop is preferred since there's afunction-call overhead in calling BLAS routines.* More tests. We should (at least) have a test for every errorcondition.  Use GCOV to improve coverage.* Annotate the header files with GAMS classifications.  See if theycan be included in the GAMs website.* Make the return value EINVAL vs EDOM consistent for invalidparameters. EDOM means a domain error (i.e. float or mathematicallyundefined), EINVAL means invalid (i.e. zero length)* Change return 0 to return GSL_SUCCESS, and return -1 to GSL_FAILUREthroughout, where appropriate. Similarly change any if(...) checks ofreturn values to use == GSL_SUCCESS, if they are checking for zero.N.B. want to be careful about accidentally omitting error conditionsif using something like == GSL_FAILURE when function returns adifferent error code.* Make sure that all #defines are fully wrapped in ()'s, especiallythe outermost layer which may have been missed. Everything should beof the form #define foo(x) (....) so there is no possibility of badparsing.  Need a perl script to check this!* Clean up the ordering of lines in the Makefile.am's so that they areall consistent. At the moment the lines are in any order.* Eliminate use of volatile where it has been used to force rounding(integration/). It is better to write the code to avoid dependence onrounding.* Constant objects (like gsl_roots_fsolver_brent) ought to haveconstant pointers (const gsl_roots_fsolver_type * constgsl_roots_fsolver_brent)* PyGSL -- python bindings for GSL, see http://pygsl.sf.net/Wishlist or vague ideas=======================* An example chapter on how to link GSL code with GNU Guile, and PythonWe could also provide g-wrap wrappers for guile, or swig.i files andswig demos so that swig can be run more easily.* Provide an interface to LAPACK, as for BLAS?  Clarify the licensefor LAPACK first, their web page is vague on what the license termsare.  Some parts of LAPACK are included in octave so maybe the Octavemaintainers will know more.* Public domain or free texts which could be distributed with GSL:     Abramowitz and Stegun, "Handbook of Mathematical Functions" appears tobe public domain.SEPT/02: See online images at http://members.fortunecity.com/aands/Devroye's book on Random Variates (1st ed) is/was in the publicdomain.  * Investigate complex support in GCC: Operations like sin(z) silentlyconvert argument to double, losing the imaginary part. This ismentioned in CEPHES documentation in 1998 with a patch to generate awarning.  What happened? (Does it now work with gcc-3.0?)* Go through the matrix and vector functions systematically and decidewhat should be provided outside of BLAS.* Standardize function names, in particular VERB vs NOUN (e.g. _invertvs _inverse). Also adopt a convection for functions which can operatein place vs use of workspace (e.g linalg_solve functions).* Change from gsl-ref.texi to gsl.texi since it is the main file?Also, put under dir section "Math" (which seems to be the appropriateone for Debian, as Octave, Gnuplot etc are in that)* Remove error stream stuff?? It is hardly used.* Extend histogram routines as described in recent discussion* Check that there are no conflicts when linking with Lapack. CBLAS, ATLAS* Make a sorted datatype for the median and quantile functions so thatthe user can be prevented from passing unsorted data, which is notchecked for.* Optimization/error for dest == src as appropriate* Provide a run-time expression evaluator for interactive programswhere the user can provide formulas as strings.  Keith Briggsrecommended formulc2.22 which he had found useful in several projects.http://www.cs.brandeis.edu/~hhelf/formu/formulc.html. It is LGPL.Alternatively, the source code for GDB contains yacc grammars andevaluators for expressions in various languages, so that would beanother way to go.  It would have the advantage of following thelanguage standards.  If I was going to write something from scratch Iwould think about using that as a base, as the full set of operatorsare already included with the correct precedence rules. Being able toevaluate C and Fortran expressions could be useful.* We should have an index mapping type object which handles elementsof size_t for vectors and matrices, or at least vectors and matricesof size_t in addition to long, int, etc.