From: Brian Gough <bjg@network-theory.co.uk>
To: Patrick Alken <patrick.alken@colorado.edu>
Cc: gsl-discuss@sourceware.org
Subject: Re: [Help-gsl] Submitted patch to add bspline derivative capabilities
Date: Thu, 11 Dec 2008 17:03:00 -0000 [thread overview]
Message-ID: <m38wqsjhis.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <20081205191058.GA11218@hippogriff.homeunix.org>
At Fri, 5 Dec 2008 12:10:58 -0700,
Patrick Alken wrote:
> Ah I hadn't considered this issue. If there are other areas of GSL
> which have the same issues maybe we should keep a list so when there
> is a major new release like 2.0 we could integrate these "extra"
> workspaces?
I've put the following in the toplevel TODO file. We should
probably make 2.0 the next release after this.
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)
> Of course one problem with that is if we have a separate workspace
> for bspline derivatives it may never be convenient to integrate it
> with the normal bspline workspace.
True, unfortunately I don't see any easy way round that.
prev parent reply other threads:[~2008-12-07 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a00655d0811191412t371982eev1bb77325719860f7@mail.gmail.com>
2008-11-19 23:42 ` Patrick Alken
2008-12-07 12:29 ` Brian Gough
2008-12-08 21:12 ` Patrick Alken
2008-12-08 21:43 ` Brian Gough
2008-12-09 9:15 ` Patrick Alken
[not found] ` <4a00655d0811291850u684d1cd8k2bab8c651045cb11@mail.gmail.com>
2008-12-09 22:58 ` Patrick Alken
2008-12-10 18:25 ` Brian Gough
2008-12-11 12:52 ` Patrick Alken
[not found] ` <4a00655d0812051440v46865adbsfcc10bb7dce28d98@mail.gmail.com>
2008-12-11 15:18 ` Rhys Ulerich
2008-12-12 11:14 ` Brian Gough
2008-12-12 12:19 ` Rhys Ulerich
2008-12-12 17:20 ` Brian Gough
2008-12-11 17:03 ` Brian Gough [this message]
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=m38wqsjhis.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sourceware.org \
--cc=patrick.alken@colorado.edu \
/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).