From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: MON KEY Newsgroups: gmane.emacs.devel Subject: Re: persistent lisp objects Date: Fri, 2 Oct 2009 16:55:15 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1254519513 27812 80.91.229.12 (2 Oct 2009 21:38:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Oct 2009 21:38:33 +0000 (UTC) Cc: Thierry Volpiatto To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 02 23:38:26 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MtppZ-00014L-6W for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2009 23:38:25 +0200 Original-Received: from localhost ([127.0.0.1]:55174 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtppY-0004Ml-Ez for ged-emacs-devel@m.gmane.org; Fri, 02 Oct 2009 17:38:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mtp9v-0002iG-4S for emacs-devel@gnu.org; Fri, 02 Oct 2009 16:55:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mtp9p-0002gU-Pf for emacs-devel@gnu.org; Fri, 02 Oct 2009 16:55:22 -0400 Original-Received: from [199.232.76.173] (port=34349 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mtp9p-0002gR-MN for emacs-devel@gnu.org; Fri, 02 Oct 2009 16:55:17 -0400 Original-Received: from mail-yx0-f191.google.com ([209.85.210.191]:61328) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mtp9p-0005o2-BB for emacs-devel@gnu.org; Fri, 02 Oct 2009 16:55:17 -0400 Original-Received: by yxe29 with SMTP id 29so440408yxe.14 for ; Fri, 02 Oct 2009 13:55:16 -0700 (PDT) Original-Received: by 10.150.17.5 with SMTP id 5mr5157661ybq.195.1254516915414; Fri, 02 Oct 2009 13:55:15 -0700 (PDT) X-Google-Sender-Auth: e5256aee23e1a205 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:115872 Archived-At: Thierry Volpiatto 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