From: Jan Moringen <jan.moringen@uni-bielefeld.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Thu, 31 Dec 2009 04:16:27 +0100 [thread overview]
Message-ID: <947_1262229391_ZZg0N0K4lExer.00_1262229387.3761.36.camel@localhost.localdomain> (raw)
In-Reply-To: <E1NPrKD-0006Y5-0F@fencepost.gnu.org>
On Wed, 2009-12-30 at 00:42 -0500, Eli Zaretskii wrote:
> > Date: Wed, 30 Dec 2009 03:49:00 +0100
> > From: Jan Moringen <jan.moringen@uni-bielefeld.de>
> >
> > Basically, I implemented an algorithm (c3 linearization) which is
> > described in an academic paper (see below). My implementation is
> very
> > close to the implementation presented in the paper (although that
> one is
> > written in Dylan).
> > [...]
> > Any thoughts on this issue would be greatly appreciated. I can try
> to
> > provide additional information if required.
>
> To my non-lawyer's eyes, the two implementations are so different in
> form that they only share the same idea. And ideas are not
> copyrightable, AFAIK.
Thanks for the assessment. That line of thought did not cross my mind. I
assumed one had to make the argument under the assumption that my code
is derived from the presented Dylan code (which it is).
Jan
next prev parent reply other threads:[~2009-12-31 3:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 2:49 Potential copyright problem in EIEIO improvement Jan Moringen
2009-12-30 5:42 ` Eli Zaretskii
2009-12-31 3:16 ` Jan Moringen [this message]
2009-12-31 1:45 ` Richard Stallman
2009-12-31 3:25 ` Jan Moringen
2010-01-01 2:55 ` Richard Stallman
2010-01-01 18:52 ` Jan Moringen
2010-01-02 15:45 ` Richard Stallman
2010-01-03 18:52 ` Jan Moringen
2010-01-04 4:09 ` Richard Stallman
2010-01-04 5:37 ` Jan Moringen
2010-01-04 16:23 ` Richard Stallman
2010-01-05 4:23 ` Jan Moringen
2010-01-05 20:45 ` Richard Stallman
2010-01-06 8:11 ` David Kastrup
2010-01-30 21:32 ` Richard Stallman
2010-02-01 3:02 ` Jan Moringen
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=947_1262229391_ZZg0N0K4lExer.00_1262229387.3761.36.camel@localhost.localdomain \
--to=jan.moringen@uni-bielefeld.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).