unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: Can Ebrowse or ECB give me a list of functions called? Or something else?
Date: Fri, 06 Aug 2004 12:19:58 +0300	[thread overview]
Message-ID: <1659-Fri06Aug2004121957+0300-eliz@gnu.org> (raw)
In-Reply-To: <nb3uec.36.ln@acm.acm> (message from Alan Mackenzie on Thu, 5 Aug 2004 19:55:35 +0000)

> From: Alan Mackenzie <acm@muc.de>
> Newsgroups: gnu.emacs.help
> Date: Thu, 5 Aug 2004 19:55:35 +0000
> 
> We have a source tree of mixed C and C++.  Management is considering
> "just" switching to a different unix-like OS.  I have been tasked with
> discovering exactly which functions (from the OS and standard libraries)
> are called.
> 
> Before embarking on the writing of a script to parse our source files, I
> was wondering if I could somehow extract the information from an Ebrowse
> or ECB database file.  Clearly a TAGS file doesn't contain the requisite
> info.

I'd begin with GNU ID-Utils.  They generate a database of all the
symbols in a source tree, and let you run queries on that adatabase.
There's a nice grep-like Emacs inteface to the most frequently-used
query (find all the lines where a certain symbol or a symbol-name
pattern is mentioned), but even if you use the less frequent queries
outside Emacs, you could then add some simple scripts on top of that.

Look at the GNU FTP site for the latest version of ID-Utils.  I find
it a must when browsing a large source tree.

  reply	other threads:[~2004-08-06  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 19:55 Can Ebrowse or ECB give me a list of functions called? Or something else? Alan Mackenzie
2004-08-06  9:19 ` Eli Zaretskii [this message]
     [not found] ` <mailman.107.1091784426.2011.help-gnu-emacs@gnu.org>
2004-08-15 13:53   ` Alan Mackenzie
2004-08-16 19:26     ` Eli Zaretskii

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=1659-Fri06Aug2004121957+0300-eliz@gnu.org \
    --to=eliz@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.
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).