unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <usenet@informatimago.com>
Subject: Re: Finding Unused Identifiers
Date: Fri, 03 Mar 2006 12:25:07 +0100	[thread overview]
Message-ID: <87y7zrhiss.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: 1kwdawrs69lxs$.1nqpbp8apcebt.dlg@40tude.net

Peter Tury <tury.peter@gmail.com> writes:

> On Thu, 02 Mar 2006 22:25:10 GMT, August Karlstrom wrote:
>
>> I mean "forgotten" variables and functions that were never intended to 
>> be exported. I know that in Elisp all identifiers with file scope are 
>> exported, but it would be nice to at least have a list of all 
>> declared-but-never-used-in-the-same-file identifiers. That would give 
>> you an hint of what can safely be removed.
>> 
>
> As the first easiest(?) step it might help if you generate a list of all
> words what has only one instance in that file (and that instance is in an
> outermost defvar...)? If the list would have a form what is usable in
> compilation mode, then one could go throught it easily and check what
> should really be removed...

(require 'cl)
(require 'pjb-sources)
;; http://www.informatimago.com/develop/emacs/                           

(let ((defvars '())
      (refered '()))
  (flet ((push-refered (form)
           (cond ((symbolp form)
                  (push form refered))
                 (t (while (consp form)
                      (push-refered (car form))
                      (setf form (cdr form)))))))
    (map-sexps "/home/pjb/src/public/emacs/pjb-sources.el"
               (lambda (form start end)
                  (if (and (consp form) (eq 'defvar (first form)))
                     (progn (push (second form) defvars)
                            (and (third form) (push-refered (third form))))
                     (push-refered form)))
              :deeply nil :atoms t)
   (print defvars)
   (set-difference defvars refered)))

Prints:

(dummy line-num-map *silent* *pjb-sources-initials* *map-sexps-function*
 *map-sexps-atoms* *map-sexps-deeply* *map-sexps-top-level*
 *walk-sexps-end-marker* update-def-names-minimum-lines update-def-names
 *greek-flk* pretty-greek)

and returns:

(dummy)

                   
-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

WARNING: This product warps space and time in its vicinity.

  reply	other threads:[~2006-03-03 11:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 13:31 Finding Unused Identifiers August Karlstrom
2006-03-02 14:07 ` Markus Triska
2006-03-02 15:13   ` B. T. Raven
2006-03-02 17:18     ` Markus Triska
2006-03-02 22:25     ` August Karlstrom
2006-03-03  8:39       ` Peter Tury
2006-03-03 11:25         ` Pascal Bourguignon [this message]
2006-03-03 13:31           ` Markus Triska
2006-03-04  2:21             ` Pascal Bourguignon
2006-03-04 15:20               ` Markus Triska
2006-03-04 19:19         ` August Karlstrom
2006-03-05  3:15           ` August Karlstrom
2006-03-05 15:13             ` Markus Triska
2006-03-05 16:05               ` August Karlstrom
2006-03-08 18:43                 ` Kevin Rodgers
     [not found]                 ` <mailman.88.1141843635.2832.help-gnu-emacs@gnu.org>
2006-03-09 13:08                   ` August Karlstrom

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87y7zrhiss.fsf@thalassa.informatimago.com \
    --to=usenet@informatimago.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).