all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Cc: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: Re: persistent lisp objects
Date: Fri, 2 Oct 2009 16:55:15 -0400	[thread overview]
Message-ID: <d2afcfda0910021355m53aa23a5jb3e36c2c1a64b1b0@mail.gmail.com> (raw)

Thierry Volpiatto <address@hidden> writes:
> This is a feature of `eval-when-compile' that is not documented.
> It can be interesting as AFAIK there is no way to save object.

What would are consequence for this type of output vis a vis GPL? e.g.:

,----
| In what cases is the output of a GPL program covered by the GPL too?
|
|     Only when the program copies part of itself into the output.
`----
See: (URL `http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL')

Likewise, for the GFDL?

This technique's ability to provide compiled persistence of symbols
would imply an ability to provide compiled persistence of the symbol's
value as well. Couldn't that have implications when those symbols
carry values for 'code writing code'?

For example, doesn't GNU Bison have "special" licensing consideration
to accommodate similar quandary?

s_P

s_P




             reply	other threads:[~2009-10-02 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 20:55 MON KEY [this message]
2009-10-03  3:36 ` persistent lisp objects 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
  -- 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=d2afcfda0910021355m53aa23a5jb3e36c2c1a64b1b0@mail.gmail.com \
    --to=monkey@sandpframing.com \
    --cc=emacs-devel@gnu.org \
    --cc=thierry.volpiatto@gmail.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.