From: Brian Auld <brian.auld@lefthandnetworks.com>
Subject: using id-utils/mkid/gid with C++ instead of C
Date: Tue, 10 Feb 2004 15:35:03 -0700 [thread overview]
Message-ID: <40295C97.7000201@lefthandnetworks.com> (raw)
Hi,
I've been a satisfied id-utils user for the past year. I was recently
confronted with C++ code and appear to be running into problems. For
example:
1st file: class.h:
--------------------
...
class class_A{
func_A();
...
};
...
2nd file: lib.cpp
--------------------
...
class_A::func_A(){
...
}
...
3rd file main.cpp
---------------------
main(){
...
class_A::func_A();
...
}
When I run mkid/gid on the function: func_A, the only hit I get is the
member function declaration in the 1st file. Am I missing something
here. Is there a trick to get 'gid' to work better with C++ code? I
checked man pages and the email archives, but wasn't able to come up
with anything helpful. When I run 'gid' on func_A, I'd like to get hits
for all 3 file occurences above.
Thanks,
Brian
next reply other threads:[~2004-02-10 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 22:35 Brian Auld [this message]
2004-02-11 8:39 ` using id-utils/mkid/gid with C++ instead of C Eli Zaretskii
2004-02-11 14:50 ` Brian Auld
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=40295C97.7000201@lefthandnetworks.com \
--to=brian.auld@lefthandnetworks.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).