From: Jan Moringen <jan.moringen@uni-bielefeld.de>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Fri, 01 Jan 2010 19:52:49 +0100 [thread overview]
Message-ID: <28416_1262371970_ZZg0N5T~46u9H.00_1262371969.3761.1205.camel@localhost.localdomain> (raw)
In-Reply-To: <E1NQXfY-0002NT-Fx@fencepost.gnu.org>
On Thu, 2009-12-31 at 21:55 -0500, Richard Stallman wrote:
> Thank you for your opinion on this. Regarding the "if" part, there
> are
> two parts: the canonical Dylan linearization, upon which the paper
> (mentioned in my original message) is improving and the actual
> improvement. The code above corresponds to the improvement. My
> patch
> also has parts derived from the unchanged parts of the canonical
> implementation.
>
> You have lost me; I can't follow the scenario.
Sorry. Let me start over.
I would like to contribute an improvement to EIEIO which consists of the
implementation of an algorithm (called c3 linearization) for computing
class precedence lists. My implementation in Emacs Lisp is based on an
implementation in Dylan that has been published in an academic paper
[1].
The Dylan code presented in that paper consists of two parts: the class
precedence list computation currently used in Dylan and an improved
version (the c3 linearization). Two thirds of the improved version are
identical to the old implementation. The old implementation is available
under GPL, for example in Open Dylan.
My code is derived from both parts of the Dylan code.
> What I can say is that, in general, we do not want to incorporate
> code into Emacs without a copyright assignment.
I have written all the code that would go into EIEIO and I have signed
the copyright assignment forms for both GNU Emacs and CEDET. The
copyright assignment should not be a problem. The question Eric and I
could not answer is whether incorporating my code and assigning the
copyright could lead to copyright problems because of the way that code
came into existence.
Kind regards,
Jan
[1] Kim Barrett et al.: A Monotonic Superclass Linearization for Dylan
http://192.220.96.201/dylan/linearization-oopsla96.html
next prev parent reply other threads:[~2010-01-01 18:52 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
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 [this message]
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='28416_1262371970_ZZg0N5T~46u9H.00_1262371969.3761.1205.camel@localhost.localdomain' \
--to=jan.moringen@uni-bielefeld.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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).