From: Khamis Abuelkomboz <khamis@knuut.de>
To: alex.shneer@verizon.com
Cc: irox@redhat.com, sourcenav@sources.redhat.com
Subject: Re: cross references of static functions
Date: Thu, 18 Jan 2001 00:53:00 -0000 [thread overview]
Message-ID: <3A66AE81.A39B33F1@knuut.de> (raw)
Hi alex,
The functionality exists in SN, you need to hit the right-mouse
button in the xref view and click on "Compare static information".
have fun!
khamis
==
Hi,
can anybody tell why cross reference window shows that both func1 and
func2
are referenced by static_func,
no matter wich one we choose: one defined in the static1.c or one
defined
in static2.c?
static1.c:
--------------------------------------
static static_func()
{
func1();
}
--------------------------------------
static2.c
--------------------------------------
static static_func ()
{
func2();
}
---------------------------------------
next reply other threads:[~2001-01-18 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 0:53 Khamis Abuelkomboz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-18 6:25 alex.shneer
2001-01-18 7:26 ` Khamis Abuelkomboz
2001-01-10 13:47 alex.shneer
2001-01-10 13:01 alex.shneer
2001-01-10 13:23 ` Ian Roxborough
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=3A66AE81.A39B33F1@knuut.de \
--to=khamis@knuut.de \
--cc=alex.shneer@verizon.com \
--cc=irox@redhat.com \
--cc=sourcenav@sources.redhat.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).