public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Keogh, Craig" <keogh@rlmsystems.com.au>
To: "'T Alexander'" <alexandert_in@yahoo.co.uk>
Cc: "'sourcenav@sourceware.cygnus.com'" <sourcenav@sourceware.cygnus.com>
Subject: RE: Help on Source Navigator parser
Date: Thu, 09 Aug 2001 16:56:00 -0000	[thread overview]
Message-ID: <34168E9E775CD411A4430000F80768621B4434@unclassfs03.rlmsystems.com.au> (raw)

> what i want to know is
> that wether we'll be able to use the parser by itself
> to create a database of the cross-refernce and all
> without running the snavigator.

You can run the C++ parser, cbrowser, from the command line:
cbrowser -y files.f -p /bin/more

Where files.f is a list of files to parse, which you can generate with
ls -1 *.c* > files.f

But this won't build you a database.

Look at \source\snavigator\hyper\sn.h

Write your own functions of the prototypes listed there.
Eg:

int put_cross_ref ((int type,int scope_type,int scope_lev,
   char *fnc_cls,char *fnc,char *fnc_arg_types,char *scope,char *what,
   char *arg_types,char *file,int lineno,int acc))
{
  cout << type << scope_type << scope_level << fnc_cls << fnc
       << fnc_arg_types << scope << what << arg_types << file
       << lineno << acc << endl;
}

And link cbrowser against your own implemenation.
Run it with:
cbrowser -y files.f -p /bin/more

Of course, I don't recommend doing this. Use a compiler compiler tool, and 
do it yourself.

Craig Keogh

             reply	other threads:[~2001-08-09 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 16:56 Keogh, Craig [this message]
2001-08-13  0:17 ` T Alexander
  -- strict thread matches above, loose matches on Subject: below --
2001-08-09  2:22 T Alexander
2001-08-08  3:23 Help on source navigator Parser Alexander T

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=34168E9E775CD411A4430000F80768621B4434@unclassfs03.rlmsystems.com.au \
    --to=keogh@rlmsystems.com.au \
    --cc=alexandert_in@yahoo.co.uk \
    --cc=sourcenav@sourceware.cygnus.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).