From: Brian Gladman <brg@gladman.plus.com>
To: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: Issue with Mathieu Function Code
Date: Mon, 09 Sep 2013 19:25:00 -0000 [thread overview]
Message-ID: <522E20BE.60002@gladman.plus.com> (raw)
In-Reply-To: <522E1BB5.9070506@gladman.plus.com>
On 09/09/2013 20:04, Brian Gladman wrote:
> On 09/09/2013 18:50, Patrick Alken wrote:
>> This sounds like a good idea, but we need to maintain binary
>> compatibility in future releases of GSL. It seems we could easily add
>> functions with _e names, since they are already implemented. But we need
>> to maintain the old interfaces as well, or at least mark them as
>> deprecated, so that people can link their programs to the new library
>> version without needing to recompile.
>
> Ah, I hadn't realised that this was an issue.
>
> Is there a define somewhere (or could we add one) that would allow
> those users who are happy to recompile to update to a new interface?
>
> What I have in mind is to have
>
> ---------------------------------
> // the new function
> int function_e(...)
> {
> }
>
> #ifdef MAINTAIN_BINARY_COMPATIBILITY
>
> // keep the old function
> #define function function_e
>
> #else
>
> // add the new function
> double function(...)
> {
> EVAL_RESULT(function_e(order, qq, zz, &result));
> }
>
> #endif
>
> This would also make it easy to move to v2.0.
Answering my own question, I could simply use GSL_MAJOR_VERSION
Brian
prev parent reply other threads:[~2013-09-09 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 18:11 Brian Gladman
2013-09-09 17:50 ` Patrick Alken
2013-09-09 19:04 ` Brian Gladman
2013-09-09 19:25 ` Brian Gladman [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=522E20BE.60002@gladman.plus.com \
--to=brg@gladman.plus.com \
--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).