From: Brian Gough <bjg@network-theory.co.uk>
To: Patrick Alken <patrick.alken@colorado.edu>
Cc: gsl-discuss@sourceware.org, Rhys Ulerich <rhys.ulerich@gmail.com>
Subject: Re: [Help-gsl] Submitted patch to add bspline derivative capabilities
Date: Wed, 10 Dec 2008 18:25:00 -0000 [thread overview]
Message-ID: <m3d4g6jvsg.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <20081129214241.GA15002@hippogriff.homeunix.org>
I noticed a problem when preparing the new release. The extra entries
in the bspline derivatives workspace break binary compatibility.
This isn't necessarily a huge problem, but it seems undesirable to
force an upgrade of all applications just for those two struct
entries. If we're going to break binary compatibility we may as well
do it for all other functions that need it at the same time.
So I'd propose using a separate workspace for the derivative functions
in this release.
See e.g. branch bspline-compat at http://src.network-theory.com/gsl.git/
which is basically finished, I just need to add some error checking.
next prev parent reply other threads:[~2008-12-05 18:58 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 [this message]
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
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=m3d4g6jvsg.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sourceware.org \
--cc=patrick.alken@colorado.edu \
--cc=rhys.ulerich@gmail.com \
/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).