[Top][All Lists]

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

Re: Report the evolution of Emacs Lisp sources.

From: Thien-Thi Nguyen
Subject: Re: Report the evolution of Emacs Lisp sources.
Date: Tue, 19 Aug 2008 15:22:34 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

() A Soare <address@hidden>
() Mon, 18 Aug 2008 12:14:45 +0200 (CEST)

   Yes, it could generate a simple prototype for change logs... as
   application. When you cut, add, or modify an old structure it
   will immediately see that.

The analysis described in the paper you referenced is very
superficial compared to what is possible w/ elisp.  For example,
you can use byte-compiler properties (e.g., no side-effects) to
report the safety of a change.

   But note that if you work on version X from the day x, you must
   keep the original from the day x, otherwise it will detect in
   your report the changes made by others!

Actually, reporting the changes made by others is exactly what i
had in mind.  Sometimes what people write in ChangeLog files is
better understood w/ a little help from a "second opinion".


reply via email to

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