From: Richard Stallman <rms@gnu.org>
To: MON KEY <monkey@sandpframing.com>
Cc: emacs-devel@gnu.org
Subject: Re: persistent lisp objects
Date: Sun, 04 Oct 2009 17:03:13 -0400 [thread overview]
Message-ID: <E1MuYEb-00045L-Vl@fencepost.gnu.org> (raw)
In-Reply-To: <d2afcfda0910031715h5187558atc68d7e1d55b6c35@mail.gmail.com> (message from MON KEY on Sat, 3 Oct 2009 20:15:27 -0400)
> The copyright on compiler output follows the copyright on the input
> that was compiled. In other words, the copyright holder of the input
> also has the copyright on the output.
So, if the output produced of the compiler originates by a method
dispatched on a
subclassed object it would be under GPL?
I do not follow you.
I am not sure what scenario you mean.
There are two questions here (and in any such case): who holds the
copyright, and whether there is any constraint on the license that the
copyright holder can release under. What I spoke about is who holds
the copyright.
What of cases where one or more methods so specialized act in concert to snarf
data from some other source(s) where these sources are extraneous to the local
handlers - e.g. the GPL'd objects/methods?
data -> object -> method -> compiled-output
That is very abstract. It is hard to consider these issues in the abstract.
Only a concrete scenario has all the details that affect the answer.
next prev parent reply other threads:[~2009-10-04 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 20:55 persistent lisp objects MON KEY
2009-10-03 3:36 ` Stefan Monnier
2009-10-03 19:19 ` MON KEY
2009-10-03 20:13 ` Richard Stallman
2009-10-04 0:15 ` MON KEY
2009-10-04 21:03 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-29 8:50 Thierry Volpiatto
2009-10-01 8:14 ` Thierry Volpiatto
2009-10-07 16:53 ` Drew Adams
2009-10-07 22:03 ` Stefan Monnier
2009-10-07 22:10 ` Drew Adams
2009-10-08 5:11 ` Stephen J. Turnbull
2009-10-25 10:33 ` Thierry Volpiatto
2009-10-25 10:26 ` Thierry Volpiatto
2009-10-25 15:05 ` Stefan Monnier
2009-10-27 20:18 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MuYEb-00045L-Vl@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monkey@sandpframing.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.