Dave Moon had some ideas [1] about how s-expressions are a nonmodern
way to store code; he mentioned annotations would be nice. I think it
would be useful for things like IDEs to associate version control info
with code. Has anyone written a paper or talked about annotations?
Thanks for any pointers.
[1] http://www.archub.org/arcsug.txt
Tayssir John Gabbour wrote:
> Dave Moon had some ideas [1] about how s-expressions are a nonmodern
> way to store code; he mentioned annotations would be nice. I think it
> would be useful for things like IDEs to associate version control info
> with code. Has anyone written a paper or talked about annotations?
>
> Thanks for any pointers.
>
> [1] http://www.archub.org/arcsug.txt
It seems to me that his suggestions are similar to what syntax-objects
in some Scheme implementations provide. (But this is only a guess.)
Pascal
--
1st European Lisp and Scheme Workshop
June 13 - Oslo, Norway - co-located with ECOOP 2004
http://www.cs.uni-bonn.de/~costanza/lisp-ecoop/
Pascal Costanza <········@web.de> wrote in message news:<············@newsreader2.netcologne.de>...
> Tayssir John Gabbour wrote:
> > Dave Moon had some ideas [1] about how s-expressions are a nonmodern
> > way to store code; he mentioned annotations would be nice. I think it
> > would be useful for things like IDEs to associate version control info
> > with code. Has anyone written a paper or talked about annotations?
> >
> > Thanks for any pointers.
> >
> > [1] http://www.archub.org/arcsug.txt
>
> It seems to me that his suggestions are similar to what syntax-objects
> in some Scheme implementations provide. (But this is only a guess.)
Thanks, it appears from the plt scheme docs I could associate a UID
with every form in a codebase. One application that seems oddly useful
to me (though I don't yet know the use) is to have every macroexpanded
form associated with the form which expanded it. (macroexpand-1.)