On Fri, 2010-01-15 at 21:36 -0800, Derick Eddington wrote: > On Fri, 2010-01-15 at 20:36 -0600, Eduardo Cavazos wrote: > > > But information like author, a one line summary, a detailed description, > > etc. are not stored in a standard way. > > > > Here's one method I experimented with... A library form has the > > structure: > > > > (library NAME EXPORT-FORM IMPORT-FORM ...) > > > > After the IMPORT-FORM I have an alist: > > > > '((author . "Billy Meier") > > (summary . "Pleiadean communications protocol") > > (description . "... long description goes here") > > (license . ...) > > (project-page . ...) > > (repository . "git://...")) > > > > If we included such information in our libraries, it would be > > straighforward to have a generated list of the communities libraries. > > Also, it would be of use for library browsing utilities intended for use > > on the local workstation. > > > > A quoted alist after IMPORT-FORM is harmless. > > Actually, it's illegal, if there are definitions after it, because > expressions cannot precede definitions in a library body.
Also, it would be problematic if 'quote' is bound to something different or not imported. -- : Derick ----------------------------------------------------------------
