From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: byte-compile-call-tree
Date: Wed, 15 Jan 2014 16:59:37 +0100 [thread overview]
Message-ID: <8761pl5j86.fsf@web.de> (raw)
Hello,
`byte-compile-call-tree' is a great source of information about a
library created as side effect when compiling. The information is more
complete and reliable that one could reach easily with other means.
1. Currently, AFAIK the only mean to get the call tree is to bind
`byte-compile-generate-call-tree' and compile. The problem is that view
people know that, I think. It would be better if there was a command
available that one can find.
2. There's even no mean to get the call tree as an expression without
hacking bytecomp.el. The tree is destroyed by `display-call-tree' that
prints the output to a buffer.
3. To the programmer, the current output is not so useful as such.
Programmers have questions like "do I use cl stuff in my lib, or can I
avoid to require cl-lib?". Or "I want to get rid of using lib-foo in my
package - which of my functions call its function and which?". It is
quite easy to extract this information from the call tree and sort stuff
by library (in a ~30 lines).
I first wanted to write a library for this kind of stuff, but I wonder
if we should better do this in Emacs.
Regards,
Michael.
next reply other threads:[~2014-01-15 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 15:59 Michael Heerdegen [this message]
2014-01-15 17:31 ` byte-compile-call-tree Stefan Monnier
2014-01-15 18:24 ` byte-compile-call-tree Michael Heerdegen
2014-01-15 19:27 ` byte-compile-call-tree Michael Heerdegen
2014-01-18 15:38 ` byte-compile-call-tree Michael Heerdegen
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=8761pl5j86.fsf@web.de \
--to=michael_heerdegen@web.de \
--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.