From: Brian Gough <bjg@gnu.org>
To: Tuomo Keskitalo <Tuomo.Keskitalo@iki.fi>
Cc: GSL Discuss Mailing List <gsl-discuss@sourceware.org>
Subject: Re: GSL 2.0 roadmap
Date: Fri, 21 Aug 2009 20:42:00 -0000 [thread overview]
Message-ID: <m3r5v4527i.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <4A7ADFDC.9080408@iki.fi>
Sorry for the delay in replying. Here's a list of the changes from
the NOTES file and my own org file. I plan to make a branch for
release 2.0 after the next release 1.13 which will hopefully be next
week. The 1.x branch should probably be maintained in parallel with
any bug fixes for a release or two but hopefully those are just minor
things now which we can easily merge.
* Changes for Release 2.0
Break binary compatibility, but keep source compatibility.
** Add a 'void *' to all workspaces, to allow for future changes.
** Disable deprecated functions
** Fix up the workspace_alloc functions so they have consistent names
(add functions where needed, don't remove)
** Standardize function names, in particular VERB vs NOUN (e.g. _invert
vs _inverse). Also adopt a convection for functions which can operate
in place vs use of workspace (e.g linalg_solve functions).
** gsl_sf_ellint_D - remove useless argument n?
** Change default generator to Ranlxd (check seeding) or look at improved seeding for MT
** Vegas struct is too large and control variables should go at the beginning
** Remove use of long double internally, e.g. as an accumulator in
loops. It introduces variation between platforms which is undesirable.
It should be replaced with a preprocessor variable ACC_DOUBLE so
that the user can compile the library with the old long double
behavior if desired.
** Eliminate use of volatile where it has been used to force rounding
(integration/). It is better to write the code to avoid dependence on
rounding.
** Constant objects (like gsl_roots_fsolver_brent) ought to have
constant pointers (const gsl_roots_fsolver_type * const
gsl_roots_fsolver_brent)
** Make the return value EINVAL vs EDOM consistent for invalid
parameters. EDOM means a domain error (i.e. float or mathematically
undefined), EINVAL means invalid (i.e. zero length)
** Change return 0 to return GSL_SUCCESS, and return -1 to GSL_FAILURE
throughout, where appropriate. Similarly change any if(...) checks of
return values to use == GSL_SUCCESS, if they are checking for zero.
N.B. want to be careful about accidentally omitting error conditions
if using something like == GSL_FAILURE when function returns a
different error code.
** Make sure that all #defines are fully wrapped in ()'s, especially
the outermost layer which may have been missed. Everything should be
of the form #define foo(x) (....) so there is no possibility of bad
parsing. Need a perl script to check this!
** Convert to BZR? (check GPG signing and integrity guarantees)
* Release "1.14" backwards compatible
** Add error code to all linalg svx type functions for singular matrix
** Merge integ-glfixed branch
** Fix bug #25383 use GSL_ENOPROG instead of GSL_CONTINUE in lmiterate.c
** compare new erf function
** Export dwt.c/dwt_step
** Fix relative error in integration check
next prev parent reply other threads:[~2009-08-21 20:42 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 17:07 ode-initval implicit solvers and development Tuomo Keskitalo
2008-10-01 18:29 ` Brian Gough
2008-10-09 13:22 ` Brian Gough
2008-11-02 17:35 ` Tuomo Keskitalo
2008-11-03 18:09 ` Brian Gough
2009-01-24 11:52 ` Tuomo Keskitalo
2009-02-01 17:01 ` Brian Gough
2009-02-02 17:05 ` Tuomo Keskitalo
2009-03-01 14:37 ` Tuomo Keskitalo
2009-03-03 16:34 ` Brian Gough
2009-03-05 19:47 ` Tuomo Keskitalo
2009-03-05 19:54 ` Heikki Orsila
2009-03-06 20:03 ` Brian Gough
2009-04-05 12:28 ` Tuomo Keskitalo
2009-05-01 14:05 ` Tuomo Keskitalo
2009-05-04 11:23 ` Brian Gough
2009-05-08 10:51 ` Brian Gough
2009-08-06 13:51 ` GSL 2.0 roadmap Tuomo Keskitalo
2009-08-21 20:42 ` Brian Gough [this message]
2009-08-27 11:42 ` Tuomo Keskitalo
2009-08-27 12:51 ` Robert G. Brown
2009-08-28 13:57 ` Jordi Burguet Castell
2009-08-27 17:13 ` Robert G. Brown
2009-08-28 13:58 ` Brian Gough
2009-08-27 23:10 ` Gerard Jungman
2009-08-27 23:13 ` GSL 2.0 roadmap (one man's view) Gerard Jungman
2009-08-28 13:58 ` Brian Gough
2009-09-16 0:43 ` Gerard Jungman
2009-09-03 19:37 ` Brian Gough
2009-09-16 0:44 ` Gerard Jungman
2009-09-07 15:10 ` Brian Gough
2009-09-07 15:34 ` Rhys Ulerich
2009-09-07 18:21 ` Robert G. Brown
2009-09-16 0:47 ` Gerard Jungman
2009-09-18 3:51 ` column-major Z F
2009-09-21 12:08 ` column-major Brian Gough
2009-09-07 15:10 ` GSL 2.0 roadmap (one man's view) Brian Gough
2009-09-16 0:45 ` Gerard Jungman
2009-09-20 9:36 ` Tuomo Keskitalo
2009-09-20 13:23 ` Robert G. Brown
2009-09-20 15:31 ` Rhys Ulerich
2009-09-20 16:19 ` Robert G. Brown
2009-09-21 15:13 ` Brian Gough
2009-09-20 15:08 ` Rhys Ulerich
2009-09-21 12:08 ` Brian Gough
2009-09-07 15:10 ` Brian Gough
2009-09-16 0:47 ` Gerard Jungman
2009-09-27 8:03 ` new double precision data structure? Tuomo Keskitalo
2009-09-28 8:44 ` James Bergstra
2009-09-28 15:48 ` Tuomo Keskitalo
2009-10-16 13:59 ` Brian Gough
2009-09-29 18:38 ` Gerard Jungman
2009-09-07 15:10 ` GSL 2.0 roadmap (one man's view) Brian Gough
2009-09-16 0:46 ` Gerard Jungman
2009-09-16 2:48 ` Robert G. Brown
2009-09-17 19:14 ` Brian Gough
2009-09-07 15:10 ` Brian Gough
2009-09-16 0:46 ` Gerard Jungman
2009-09-17 20:12 ` Brian Gough
2009-09-07 15:10 ` Brian Gough
2009-09-16 0:44 ` Gerard Jungman
2009-09-17 20:12 ` Brian Gough
[not found] ` <645d17210909090818u474f32f0q19a6334578b9f02c@mail.gmail.com>
2009-09-17 19:14 ` Brian Gough
2009-08-28 13:58 ` GSL 2.0 roadmap Brian Gough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r5v4527i.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=Tuomo.Keskitalo@iki.fi \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).