unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Tim Meehan <btmeehan@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Mon, 28 Jun 2021 21:50:21 +0000	[thread overview]
Message-ID: <82e31aeb-45ed-56f3-4b7f-8adeb8943c98@posteo.de> (raw)
In-Reply-To: <CACgrOxK1FNRArALUv_ZUryCk7rJwo6doSJA+Wu0aCh8EhRaauw@mail.gmail.com>

Don't take my words for words of a lawyer:

/opinion

I personally think, that something like a general algorithm cannot be limited
off and away from usage in society. I don't know about the law specifics, but if
there was a law against rewriting an algorithm, then it would be a quite stupid
law, as it would only serve to hinder progress of society.

However, as we all know the law is rarely written by experts. A lot of stupid
things are in there. It does not always take the good of society into account
and sometimes is even biased towards protecting the ones in power and with
financial resources. So it could very well be, that this is one of the cases,
where the law is stupid, or one, where it depends on what kind of day the judge
has or how well the judge knows software and code.

Furthermore I think, that rewriting the algorithm into a purely functional one
is often a significant work on its own and definitely adding enough of ones own
work to make it a separate thing in total.

/opinion end

On 6/28/21 11:38 PM, 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?
>
> Granted, I know that this is guile-user and not guile-lawyer, but in many
> cases the transformation from procedural to functional is kind of a radical
> re-imagining. I usually try to contact the people and ask them directly,
> but was wondering what was the general consensus in cases where the
> original author did not answer?

-- 
repositories: https://notabug.org/ZelphirKaltstahl




  reply	other threads:[~2021-06-28 21:50 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 [this message]
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

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=82e31aeb-45ed-56f3-4b7f-8adeb8943c98@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=btmeehan@gmail.com \
    --cc=guile-user@gnu.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).