unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 04 Jan 2010 06:37:54 +0100	[thread overview]
Message-ID: <27499_1262583480_ZZg0O354Y3InQ.00_1262583474.3761.1654.camel@localhost.localdomain> (raw)
In-Reply-To: <E1NReGC-0007oX-8t@fencepost.gnu.org>

On Sun, 2010-01-03 at 23:09 -0500, Richard Stallman wrote:
> The following piece of code is from the paper "A Monotonic
> Superclass
>     Linearization for Dylan". It is labeled "Appendix A:
> Implementation of
>     the Dylan Linearization" there. This code implements the Dylan
>     linearization *without* the improvement presented in the paper.
> 
> That is 50 lines, which is far more than enough that we would
> normally want papers.

I think, the most important part is the code in Appendix B since code
very similar to Appendix A is available in Open Dylan (I included both
in my last email). My code could have been derived from the Open Dylan
code except for the improvement presented in Appendix B.

> Can we make an exception for this case?  Maybe.  I will ask a lawyer.

Thank you for spending so much time on this.

> Which GPL versions does Open Dylan's license allow?

It is dual-licensed such that LGPL is one possible license:

=== Begin header of class-dynamic.dylan from Open Dylan ===
module:    internal
Author:    Jonathan Bachrach
Copyright:    Original Code is Copyright (c) 1995-2004 Functional Objects, Inc.
              All rights reserved.
License:      Functional Objects Library Public License Version 1.0
Dual-license: GNU Lesser General Public License
Warranty:     Distributed WITHOUT WARRANTY OF ANY KIND
=== End header of class-dynamic.dylan from Open Dylan ===

Kind regards,
Jan





  reply	other threads:[~2010-01-04  5:37 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
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 [this message]
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=27499_1262583480_ZZg0O354Y3InQ.00_1262583474.3761.1654.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).