unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Vivien Kraus via General Guile related discussions <guile-user@gnu.org>
To: tomas@tuxteam.de, Tim Meehan <btmeehan@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Tue, 29 Jun 2021 10:56:13 +0200	[thread overview]
Message-ID: <988b76b0d30bc38df920f00feaf1122fa06b542a.camel@planete-kraus.eu> (raw)
In-Reply-To: <20210629075632.GC31129@tuxteam.de>

Le mardi 29 juin 2021 à 09:56 +0200, tomas@tuxteam.de a écrit :
> On Mon, Jun 28, 2021 at 04:38:50PM -0500, Tim Meehan wrote:
> > Say for instance, I have found an algorithm for scalar function
> > minimization on a website, written in C. It is posted with a
> license for
> > use. If I write something based on this hypothetical code, is it
> then
> > clearly also licensed in the same manner?
> 
> Definitely not: a license is about copyright, and copyright protects
> the
> expression of an idea, not the idea itself (the Lord of the Rings is
> under
> copyright, but if you write a novel involving very old talking trees,
> you
> dont infringe on that).

The idea is the algorithm, but the expression of the idea is the C
program. If you copy the C program, you are indeed bound by the license
of the C program.

> You might want to not use exactly the same variable names, just to
> make sure :)

I would not do that. It will just make the program harder to read.




      reply	other threads:[~2021-06-29  8:56 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
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 [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

  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=988b76b0d30bc38df920f00feaf1122fa06b542a.camel@planete-kraus.eu \
    --to=guile-user@gnu.org \
    --cc=btmeehan@gmail.com \
    --cc=tomas@tuxteam.de \
    --cc=vivien@planete-kraus.eu \
    /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).