all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: A Soare <alinsoar@voila.fr>
To: "Emacs   Dev  [emacs-devel]" <emacs-devel@gnu.org>
Subject: Report the evolution of Emacs Lisp sources.
Date: Mon, 18 Aug 2008 09:05:19 +0200 (CEST)	[thread overview]
Message-ID: <31454827.5972821219043119737.JavaMail.www@wwinf4609> (raw)


In this moment, the only method to see how the code of emacs evaluated is `diff'.

One can show the differences, by comparing the internal representation of the lisp code tree of 2 versions. I saw this idea for the C code here: http://www.cs.umd.edu/~mwh/papers/evolution.pdf .

An advantage of this method would be to report only one when the name of a variable changes. This method will also ignore to report the null-effect characters like blanks or empty new lines. diff reports everything.

What do you think, it would be useful such a tool to make reports of lisp code changes? Maybe I will try it, but it might be _realy_ useful?



____________________________________________________

Avant de prendre le volant, repérez votre itinéraire et visualisez le trafic ! http://itineraire.voila.fr/itineraire.html






             reply	other threads:[~2008-08-18  7:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  7:05 A Soare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-20 20:53 Report the evolution of Emacs Lisp sources A Soare
2008-08-21  2:02 ` Thien-Thi Nguyen
2008-08-20 11:46 A Soare
2008-08-20 20:14 ` Thien-Thi Nguyen
2008-08-19 20:13 A Soare
2008-08-18 10:14 A Soare
2008-08-19 13:22 ` Thien-Thi Nguyen
2008-08-18  7:05 A Soare
2008-08-18  9:44 ` Thien-Thi Nguyen
2008-08-18 10:05   ` Miles Bader
2008-08-19 13:11     ` Thien-Thi Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31454827.5972821219043119737.JavaMail.www@wwinf4609 \
    --to=alinsoar@voila.fr \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.