[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: persistent lisp objects

Subject: Re: persistent lisp objects
Date: Sat, 3 Oct 2009 15:19:34 -0400

On Fri, Oct 2, 2009 at 11:36 PM, Stefan Monnier
<address@hidden> 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

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]