Re: Report the evolution of Emacs Lisp sources.

[A Soare <alinsoar@voila.fr>]

I am sorry, for the next period I will be very very "deborde" (please help me to translate). I have lots of problems much more interesting and difficult to solve and I have to finish with quickly to pass more far. But I think that I do it in future. Anyways, when I started to solve the problem of indentation, I couldn't figure a clear definition for indentation, and finally I gave a definition as an integral over the code, which can be applied for every arborescent structure (i.e. for every major mode), and I implemented it for lisp, and that will be the future code to indent lisp code in emacs. In future parse-partial-sexp will return the indetation for every major mode. That is why I consider that the problem of indentation was much more difficult, because it was fog around, no clear definition.

Alin Soare.


> Message du 20/08/08 à 22h17
> De : "Thien-Thi Nguyen" <ttn@gnuvola.org>
> A : alinsoar@voila.fr
> Copie à : "Emacs Dev [emacs-devel]" <emacs-devel@gnu.org>
> Objet : Re: Report the evolution of Emacs Lisp sources.
> 
> 
> () A Soare <alinsoar@voila.fr>
> () Wed, 20 Aug 2008 13:46:25 +0200 (CEST)
> 
>    Another application of this algorithm is to detect common
>    blocks from many different procedures. This is not an
>    improvment in the speed, but in the size of the lap.
> 
> That would be wonderful.  It's nice to have a way to find out
> which code has already been written (and how many times!).  A good
> tool for caging the ego, at the very least...
> 
> I wish you good luck finding a stopping point for your current
> activities so that you can start hacking on this.
> 
> thi
> 
> 

____________________________________________________

Des photos de vacances à partager ? Voila vous offre 1 Go d’espace de stockage. http://macle.voila.fr