From: Sergey Bochkanov <sergey.bochkanov@alglib.net>
To: gsl-discuss@sourceware.org
Subject: Re: GSL and ALGLIB
Date: Wed, 14 Apr 2010 15:11:00 -0000 [thread overview]
Message-ID: <1575429937.20100414191048@alglib.net> (raw)
In-Reply-To: <m3ljcqs94x.wl%bjg@network-theory.co.uk>
Hello, Brian.
You wrote 14 апреля 2010 г., 12:58:38:
> 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.
Yes, translator is still non-free. I think that some day I'll make it
free, but it isn't top priority for me. Just can't come to some
decision on this subject, so I am leaving this question open for a
while. And, actually, ALGLIB users rarely need something beyond the
version in the language they use.
> 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.
95% of C++ sources are as human-readable as original pseudocode.
Remaining 5% are places where C++ is used to emulate continuations -
feature lacking in many modern programming languages. However, it can
be made human-readable too (just one day or two to tweak translator)
if someone needs it. It wasn't deliberately obfuscated :)
Technically, ALGLIB can be linked to GSL and can be used under GPL
even without translator.
--
With best regards,
Sergey mailto:sergey.bochkanov@alglib.net
next prev parent reply other threads:[~2010-04-14 15:11 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
2010-04-14 15:11 ` Sergey Bochkanov [this message]
-- 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=1575429937.20100414191048@alglib.net \
--to=sergey.bochkanov@alglib.net \
--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).