Stephen J. Turnbull writes:
No direct dependencies. But it requires lots of stuff, such as
which requires cl-macs.el, which has a rather interesting hack that
seems to require a random feature (= (car features)) from the emacs
that loads it.
And you really have to trace _all_ the requires and autoloads.
(Somebody started to write a script to do all that tracing at one
time. Do I recall ... ?)
I think you may be referring to a project which I started working on
way back when I was a newcomer to the XEmacs project. I was actually
trying to do something a little more ambitious than just tracing
requires and autoloads - I was trying to devise a way to compile a
listing of every symbol which was defined in every file, and a way to
verify that if file X used symbol S defined in file Y, it did a
(require 'Y). This was around the time Steve B. was breaking
everything out into packages, and my work was intended to be a tool to
aid in this work.
I got bogged down and gave up on this, because I ran into
complications. I thought at first I could just scan files for defun,
defvar, defcustom, etc, but eventually realized that since you can
define your own macros which provide new ways to define symbols (e.g.
`defvoo' as used in gnus) simple scanning wasn't good enough. So I
gave up... maybe now that I've learned a lot more about XEmacs and
elisp it's time to scale back the scope of what I was trying to do and
pick this project up again.