From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.emacs.devel Subject: Re: Report the evolution of Emacs Lisp sources. Date: Tue, 19 Aug 2008 15:22:34 +0200 Message-ID: <87y72ti1gl.fsf@ambire.localdomain> References: <9395796.5994681219054485773.JavaMail.www@wwinf4609> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1219152367 19246 80.91.229.12 (19 Aug 2008 13:26:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Aug 2008 13:26:07 +0000 (UTC) Cc: "Emacs Dev \[emacs-devel\]" To: alinsoar@voila.fr Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 19 15:26:59 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KVREU-0000dZ-3u for ged-emacs-devel@m.gmane.org; Tue, 19 Aug 2008 15:26:46 +0200 Original-Received: from localhost ([127.0.0.1]:36312 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVRDW-0000eJ-Vh for ged-emacs-devel@m.gmane.org; Tue, 19 Aug 2008 09:25:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KVRDT-0000dm-CX for emacs-devel@gnu.org; Tue, 19 Aug 2008 09:25:43 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KVRDR-0000cv-Fs for emacs-devel@gnu.org; Tue, 19 Aug 2008 09:25:42 -0400 Original-Received: from [199.232.76.173] (port=59275 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVRDR-0000cs-9j for emacs-devel@gnu.org; Tue, 19 Aug 2008 09:25:41 -0400 Original-Received: from [151.61.140.254] (port=45638 helo=ambire.localdomain) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KVRDQ-0002w3-MA for emacs-devel@gnu.org; Tue, 19 Aug 2008 09:25:41 -0400 Original-Received: from ttn by ambire.localdomain with local (Exim 4.63) (envelope-from ) id 1KVRAQ-0002EE-78; Tue, 19 Aug 2008 15:22:34 +0200 In-Reply-To: <9395796.5994681219054485773.JavaMail.www@wwinf4609> (A. Soare's message of "Mon, 18 Aug 2008 12:14:45 +0200 (CEST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:102654 Archived-At: () A Soare () 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". thi