public inbox for
 help / color / mirror / Atom feed
From: Salman Khilji <>
To: "''" <>
Subject: Want Help with Source Navigator source code
Date: Mon, 30 Jul 2001 06:30:00 -0000	[thread overview]
Message-ID: <> (raw)

I wanted some help with the source code of the Source Navigator.  Usually,
the developers and maintainers do not like to be sent direct e-mails.  Their
e-mail addresses are:

Syd Polk
Ian Roxborough
Mo DeJong

If this is appropriate to ask, could you please forward this e-mail to them?
If not, can you please tell me who I need to contact in order to get some
help on this issue.  Here is my question:


I am developing a debugger type application for C/C++/FORTRAN (not exactly a
source line debugger).  I need access to the complete symbol table of the
target application.  This requires me to parse the source code of the
application and build a complete symbol table.  For example, I will parse
the source code and determine the type of each symbol.  For example, if a
given symbol is a structure, what are the structure members?  What is the
type of each structure member?  Ok, if a given symbol is an array, what kind
of an array is it?  What is its dimension?  Is it a multiple dimension
array?  If a given symbol is a pointer, is it pointing to a structure, a
float, etc?  Do I have an array of structures, pointers to structures etc

For this purpose, I need to have a parser for C, C++, and FORTRAN.  I have
downloaded the source code of Source Navigator.  I feel that I can somehow
extract the parsing specific code out of it and use it for my application.
The source code that I found was under the snavigator/parsers folder.
However, given the size of all the code out there, it would be hard for me
to dig into the code and find out how my main function should look like to
build a symbol table.  I'd suppose that the maintainers would know somewhat
about it and would have some sort of idea as to where and how the parsers
are used.  If you could give me pointers to where I need to look at the code
to extract parsing specific code, this would give me a great jump start.  Is
there a design documentation available that I can go through and find out
how each block of the software is put together?

Could I ask a maintainer of Source Navigator for this favor?


             reply	other threads:[~2001-07-30  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  6:30 Salman Khilji [this message]
2001-07-30 14:04 ` Mo DeJong
2001-07-30  9:40 Syd Polk

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).