From: Vivien Kraus via General Guile related discussions <guile-user@gnu.org>
To: Nate Rosenbloom <nate.rosenbloom@gmail.com>,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Tue, 29 Jun 2021 06:38:32 +0200 [thread overview]
Message-ID: <33e84ca0925be2b0ee7d04e0e2c433bdee3e1911.camel@planete-kraus.eu> (raw)
In-Reply-To: <CABESxgmdFKYetL9PdYP94jPy41P+gMOzAPGy5_pDOROtS6KyHA@mail.gmail.com>
Hello,
Le mardi 29 juin 2021 à 04:09 +0000, Nate Rosenbloom a écrit :
> since the algorithm itself
> stays the same.
This reason is not stated in the Stack Exchange post, and I believe
it’s inaccurate (although, I am not a lawyer either). I think the
reason is that you are reading the original implementation to write
your own, so you are some kind of a compiler, or translator (as for
human spoken languages). As such, what you write is mostly the other
person’s work, so you should not claim copyright about it.
However, if you are writing a computer program based on the description
of the algorithm that you would find in a peer-reviewed scientific
paper (that’s what you should be doing, because the paper will prove to
you that the algorithm is correct and efficient at solving the
problem), then it’s a different story, because copying mathematical
expressions is OK (it is proven that it’s the only correct outcome, so
there’s no copyright to claim here).
next prev parent reply other threads:[~2021-06-29 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 21:38 re-writing algorithms in Guile Tim Meehan
2021-06-28 21:50 ` Zelphir Kaltstahl
2021-06-29 4:09 ` Nate Rosenbloom
2021-06-29 4:38 ` Vivien Kraus via General Guile related discussions [this message]
2021-06-29 13:52 ` Nate Rosenbloom
2021-06-29 14:20 ` tomas
2021-06-29 23:48 ` Tim Meehan
2021-06-30 7:29 ` tomas
2021-06-29 5:26 ` Jay Sulzberger
2021-06-29 6:08 ` Dr. Arne Babenhauserheide
2021-06-29 6:08 ` Dr. Arne Babenhauserheide
2021-06-29 7:56 ` tomas
2021-06-29 8:56 ` Vivien Kraus via General Guile related discussions
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33e84ca0925be2b0ee7d04e0e2c433bdee3e1911.camel@planete-kraus.eu \
--to=guile-user@gnu.org \
--cc=nate.rosenbloom@gmail.com \
--cc=vivien@planete-kraus.eu \
--cc=zelphirkaltstahl@posteo.de \
/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).