public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@gnu.org>
To: Sergey Bochkanov <sergey.bochkanov@alglib.net>
Cc: gsl-discuss@sourceware.org
Subject: Re: GSL and ALGLIB
Date: Wed, 14 Apr 2010 08:59:00 -0000	[thread overview]
Message-ID: <m3ljcqs94x.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <758802574.20100413142051@alglib.net>

At Tue, 13 Apr 2010 14:20:51 +0400,
Sergey Bochkanov wrote:
> What  do  GSL  developers think about using source code from ALGLIB in
> GSL?   
> 
> ALGLIB  is an open source numerical analysis library distributed under
> GPL   2+.  It  uses  automatic  translation  from  specially  designed
> pseudocode  to  provide  same functionality in C++, C#, FreePascal and
> other  programming  languages.  Project  aims  to  be highly portable,
> compiler-  and  OS-independent. It is actively developed (new releases
> each month).
> 
> ALGLIB contains many interesting algorithms which are missing in GSL.
> 
> For example, it includes:
> * limited memory BFGS optimizer
> * improved Levenberg-Marquardt optimizer
> * bound constrained optimizer
> * 2-dimensional   interpolation  (bilinear/bicubic  splines)
> * scattered N-dimensional interpolation/fitting with linearithmic
>   complexity.
> 
> It  should  be easy to write GSL-ish wrapper for ALGLIB. I can help if
> someone  wants to implement it. However it is unclear what is GSL devs
> position  on  using  external libraries. I've read past discussions on
> FLAME and FFTW, but there was no decision.

Hello Sergey

Thanks for your email.  There are two concerns here, licensing and
technical.

Regarding licensing, I think we corresponded about ALGLIB a couple of
years ago and I asked if the underlying converter was free software
(which it was not at that time).  The GPL defines source code as "the
preferred form of the work for making modifications to it" -- which in
this case is the underlying algorithm definitions for the converter,
not the individual routines.  We could only consider using other code
if all the associated software (and documentation) is free.

Whether it makes sense techically to use ALGLIB in GSL, it is
difficult for me to comment without the converter being free software
and available to study.

I do think the principle of converting to different languages from a
common source is a good one and would encourage you to consider
releasing everything under a free software license, whether or not we
might use parts of it.

-- 
best regards

Brian Gough

GNU Scientific Library -
http://www.gnu.org/software/gsl/

  reply	other threads:[~2010-04-14  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  8:24 Sergey Bochkanov
2010-04-14  8:59 ` Brian Gough [this message]
2010-04-14 15:11   ` Sergey Bochkanov
  -- strict thread matches above, loose matches on Subject: below --
2010-04-13 14:17 Sergey Bochkanov

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=m3ljcqs94x.wl%bjg@network-theory.co.uk \
    --to=bjg@gnu.org \
    --cc=gsl-discuss@sourceware.org \
    --cc=sergey.bochkanov@alglib.net \
    /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).