unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Dziulko <dziulko@klaatu.canisius.edu>
Subject: Re: etags
Date: Thu, 19 Jun 2003 08:47:28 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0306190835540.19483-100000@klaatu.canisius.edu> (raw)
In-Reply-To: <160scb.f6.ln@acm.acm>

On Thu, 19 Jun 2003, Alan Mackenzie wrote:

> Kevin Dziulko <dziulko@klaatu.canisius.edu> wrote on Tue, 17 Jun 2003
> 08:09:13 -0400 (EDT):
> > Hello
> 
> > I am looking for a way to get a list of all user defined #define's in some 
> > C code that actually gets used.  I was reading up a little on etags, and I 
> > think it might help me with this.  Has anyone done or seen anything close 
> > to this?
> 
> > Example:
> > #include <stdio.h>
> > #define MSG1 "Hello, world!"
> > #define CONST1 42
> 
> > int main ()
> > {
> >     (void) printf("\n%s\n", MSG1);
> 
> >     return 0;
> > }
> 
> > /////////////////
> 
> > Idealy, I would want something to say:
> 
> > Line 7: MSG1
> 
> grep is your friend.  "man grep" should tell you all you want to know
> about it (and a lot more besides).  (I'm guessing you're on some sort of
> Unix system, by the way.)  A command something like the following will
> give you the information you want:
> 
> grep -n "^#define" *.c
> 
> You probably won't like the exact form the info takes, so you might want
> to pipe it through a small script (written in something like sed or AWK
> or Python) to massage it into something more readable.
> 
> The above command assumes that all your files.c are in the current
> directory.  If they're not, you'll have to "find" them first, then do the
> above.  Spend a few hours reading "man find"; it'll be time very well
> spent.  Then you'll end up writing something like this:
> 
> find . -name "*.c" -exec grep -n "^define" \{} \; -print
> 
> > Perhaps this isn't the best place to post this. If you know a better 
> > place, please let me know.
> 
> It isn't really the best place, no.  One of the groups on Unix shell
> commands would have been better.   But what the heck, have a great day.
> 
> > Thanks a lot!
> > Kevin
> 
> 

Thanks for your reply, but "grep -n "^#define" *.c" isn't even close to 
what I'm looking for.  I don't want a list of #define'ed constants, but 
rather #define'ed constants *THAT ACTUALLY GET USED*. That's why in my 
example I just wanted "Line 7: MSG1" and nothing about CONST1 to 
ever get listed. [also, I only want defines from my local program listed, 
and not any of the system library defines]. The cxref command is the 
closest to this that I've found thus far.

Which one of the Unix shell groups should I use?  I can't seem to find the 
right mailing list.

Thanks again!!
Kevin

  reply	other threads:[~2003-06-19 12:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8073.1055852045.21513.help-gnu-emacs@gnu.org>
2003-06-19  9:36 ` etags Alan Mackenzie
2003-06-19 12:47   ` Kevin Dziulko [this message]
2004-10-06  2:18 etags moheb missaghi
     [not found] <mailman.8237.1056026853.21513.help-gnu-emacs@gnu.org>
2003-06-19 17:42 ` etags Peter Lee
  -- strict thread matches above, loose matches on Subject: below --
2003-06-17 12:09 etags Kevin Dziulko

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=Pine.LNX.4.44.0306190835540.19483-100000@klaatu.canisius.edu \
    --to=dziulko@klaatu.canisius.edu \
    /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).