public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Kirby, Dave" <dkirby@orchestream.com>
To: "'sourcenav@sourceware.cygnus.com'" <sourcenav@sourceware.cygnus.com>
Subject: Some Python (and other) questions
Date: Mon, 02 Oct 2000 07:17:00 -0000	[thread overview]
Message-ID: <CB1E59E84CE5D3118E5C00508B6D7555723B07@s1000.orchestream.com> (raw)

I have recently upgraded to 4.5.2 for its Python support, and have some
questions.

Firstly, the python support seems to be only partial - nothing shows up in
the class view and the Xref and Include tabs are greyed out.  However the
information for the classes, methods etc are in the database since they can
be seen in the Retriever view, so what gives?  Is this a bug in the python
parser?

Secondly, has anyone tried creating python wrappers for the SN  APIs?  This
would make it easy to write scripts for analysing the information in the DB
(as suggested by a previous poster) and for creating parsers written in
python.  I may have a go myself when I have time, but dont dont want to
duplicate the work if someone else has already done it.  It should be easy
using SWIG, and this would also enable the APIs to be called from TCL, Perl,
Guile etc.


Lastly, why doesnt the mailing list digest set the 'Reply To' field?  It is
a minor point, but it would make the list much easier to use.


	Dave K

             reply	other threads:[~2000-10-02  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-02  7:17 Kirby, Dave [this message]
2000-10-02 10:41 ` Syd Polk
2000-10-02 12:22   ` Thomas Heller
2000-10-03  0:56 dave.banham

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=CB1E59E84CE5D3118E5C00508B6D7555723B07@s1000.orchestream.com \
    --to=dkirby@orchestream.com \
    --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).