From: MON KEY <monkey@sandpframing.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: persistent lisp objects
Date: Sat, 3 Oct 2009 15:19:34 -0400 [thread overview]
Message-ID: <d2afcfda0910031219r15e59c88ydaecb7f3977bfc6d@mail.gmail.com> (raw)
In-Reply-To: <jwvvdix5ex9.fsf-monnier+emacs@gnu.org>
On Fri, Oct 2, 2009 at 11:36 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> it essentially needs to be linked with Emacs (or XEmacs). So it's all
> GPL in any case.
And w/re to the GFDL?
For example, wouldn't it be possible using this technique to assemble
byte-compiled component symbols each which of itself contains only a portion of
some documentation or documentation generating routine but which is only made
manifest at compile time by virtue of this technique?
If such is possible which license would best govern the assembly of and
subsequent aggregated output from implementation of such a technique - GPL/GFDL
or both?
I ask because these types of persistence issues appear to show up in the GFDL
faq w/re Java. I'm wondering if the pending integration of CEDET eieio might
pose similar questions in the future. For example, eieio already provides some
facility for persistent documentation. Combine that with CL style `#.' symbol
dumping, this technique could pose myriad potential mechanisms for extending the
self-documenting aspects of Emacs lisp.
I've no idea if the technique Thierry presents is possible in other modern
languages (braced or curly) but certainly this one does benefit from lisp's
syntax and I suspect that historically similar approaches were made possible
leveraging CL's CLOS. That said, CLOS doesn't (in recent times) do much double
duty as "The one true editor". Likewise where CL and CLOS have existed in such
roles it is doubtful that the GFDL (or equivalent) was a factor of any
concern...
Apropos of this, it is worth considering that the first lines of the Emacs
manual begin:
,----
| You are reading about GNU Emacs, the GNU incarnation of the advanced,
| self-documenting, customizable, extensible editor Emacs.
`----(info "(emacs)Intro")
Which is immediately preceded by the section which begins:
,----
| The purpose of this License is to make a manual, textbook, or other
| functional and useful document "free" in the sense of freedom:
`----(info "(emacs)GNU Free Documentation License")
> Stefan
s_P
next prev parent reply other threads:[~2009-10-03 19:19 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 [this message]
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=d2afcfda0910031219r15e59c88ydaecb7f3977bfc6d@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.