From: "Venkatraman Rajagopalan" <r-venkatraman@ti.com>
To: <sourcenav@sources.redhat.com>
Subject: FW: Question on C language typedef hierarchy generation for source navigator
Date: Tue, 19 Nov 2002 22:54:00 -0000 [thread overview]
Message-ID: <000501c29062$fd332f20$a151579d@india.ti.com> (raw)
Hi,
I am not sure whether this is the mailing list to ask this question.
Incase this is not, please give me the mail list/group for queries on source
navigator.
Binary used and platform
-------------------------------------
I have downloaded a pre-built binary of source navigator. Am using it
for projects which contain only .c and .h files. This is a project which
does
NOT involve C++ files. The PC has WinNT
Problem
-------------
However, when parsed by source navigator. It shows the typedefs as classes
and it does not show a graphical view of the typedef elements for more than
1 level
in the hierarchy browser. In the class window, it shows all elements of the
typedefs
and their types. Whereas it shows function call-trees properly in
the hierarchy browser.
Query
-----------
Is the hierarchy browser valid only for C++ classes. How do we view the C
nested typedef / structure / element
hierarchy in source navigator.?
Any answer will be appreciated
Thanks,
Venkat
reply other threads:[~2002-11-20 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000501c29062$fd332f20$a151579d@india.ti.com' \
--to=r-venkatraman@ti.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).