From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: A Soare Newsgroups: gmane.emacs.devel Subject: Re: Report the evolution of Emacs Lisp sources. Date: Tue, 19 Aug 2008 22:13:32 +0200 (CEST) Message-ID: <27927462.5712671219176812011.JavaMail.www@wwinf4619> Reply-To: alinsoar@voila.fr NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1219176841 14135 80.91.229.12 (19 Aug 2008 20:14:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Aug 2008 20:14:01 +0000 (UTC) Cc: "Emacs Dev \[emacs-devel\]" To: Thien-Thi Nguyen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 19 22:14:53 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 1KVXbK-0004mw-B2 for ged-emacs-devel@m.gmane.org; Tue, 19 Aug 2008 22:14:46 +0200 Original-Received: from localhost ([127.0.0.1]:47902 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVXaL-00075I-Sp for ged-emacs-devel@m.gmane.org; Tue, 19 Aug 2008 16:13:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KVXaI-000754-Ps for emacs-devel@gnu.org; Tue, 19 Aug 2008 16:13:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KVXaF-00074X-KI for emacs-devel@gnu.org; Tue, 19 Aug 2008 16:13:41 -0400 Original-Received: from [199.232.76.173] (port=44480 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVXaF-00074U-Fz for emacs-devel@gnu.org; Tue, 19 Aug 2008 16:13:39 -0400 Original-Received: from smtp2.voila.fr ([193.252.22.175]:49217 helo=smtp1.voila.fr) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KVXaD-0002fR-Iz for emacs-devel@gnu.org; Tue, 19 Aug 2008 16:13:39 -0400 Original-Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf4102.voila.fr (SMTP Server) with ESMTP id 141DF1C001C7; Tue, 19 Aug 2008 22:13:32 +0200 (CEST) Original-Received: from wwinf4619 (wwinf4619 [10.232.13.63]) by mwinf4102.voila.fr (SMTP Server) with ESMTP id 047F31C001C2; Tue, 19 Aug 2008 22:13:32 +0200 (CEST) X-ME-UUID: 20080819201332186.047F31C001C2@mwinf4102.voila.fr X-Originating-IP: [93.112.92.17] X-Wum-Nature: EMAIL-NATURE X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| X-me-spamlevel: not-spam X-me-spamrating: 40.000000 X-me-spamcause: OK, (-130)(0000)gggruggvucftvghtrhhoucdtuddrvdejvddrgeejucetggdotefuucfrrhhofhhilhgvmecuoehnohhnvgeqnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenthhhvgcuphhrohgslhgvmhculddqfedtmd X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:102683 Archived-At: > 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. >=20 > 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. Yes, lap is a kind of expressing the parsing tree directly, without generat= ing parsing tree during evaluation. So you are almost right (not taking int= o account that anyways we must run for every file byte-compile instead of r= ead). In fact all the problem is to compare 2 trees (the parsed code) whose each = node keeps a key =3D and a leave has key =3D . and to report a minimum set o= f changes. >=20 > 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! >=20 > 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". >=20 true Yes, I can do it, and maybe I will do it, but later. For now I am concentra= ted on another issues. ____________________________________________________ Avant de prendre le volant, rep=C3=A9rez votre itin=C3=A9raire et visualise= z le trafic ! http://itineraire.voila.fr/itineraire.html