From: "Eray Ozkural (exa)" <erayo@cs.bilkent.edu.tr>
To: Ian Roxborough <irox@redhat.com>,
Ralf Corsepius <corsepiu@faw.uni-ulm.de>
Cc: sourcenav@sources.redhat.com, kdevelop-devel@kdevelop.org,
"Thomas Schilling" <snuffeler@gmx.net>
Subject: Re: SourceNav release ...
Date: Thu, 10 Jan 2002 04:34:00 -0000 [thread overview]
Message-ID: <E16OTwP-0000sV-00@orion.exa.homeip.net> (raw)
In-Reply-To: <20020107131412.30f223fb.irox@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ian,
Thanks a lot for all your work on sourcenav.
Is my small call graph generator included in sourcenav now? I'd posted it
here on the list. I can sign things, too. :) A fellow hacker had even made
some improvements to it. It was very useful for trying to understand a large
chunk of old code in a past project I worked in.
I have an important question to ask. For the past two weeks or so we have
been discussing how the parser backend should be in KDevelop IDE. As a
computer scientist, I feel what the Right Thing (TM) is but as far as
practically goes it is out of question [*].
What we have here is a class store API (which is basically a tree structure)
that is intended to provide type information for class based languages.
KDevelop hackers are retro-fitting a C++ parser for doing things like code
completion.
However, my hunch is that it will not be a general purpose or complete
solution to the problem. Neither is a perfect solution implementable in our
humble development environment (that being ancient parser generators and data
structure driven procedural language: C++)
The next best thing that comes to my mind is sourcenav for three reasons. It
has solved the multiple languages & persistence problems reasonably well.
And, it's very portable. Would you deem merit in trying to re-use code from
source navigator in a C++ code base? (ie we would be using the C API of
sourcenav). What advantages/disadvantages of sourcenav parser/type analysis
backend would you think of as the sourcenav maintainer? And how should one go
about it? (can the whole back end be made into a library?)
Regards,
[*] Doing incremental type analysis for all supported programming languages.
- --
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8PO0XfAeuFodNU5wRArM8AJ9VZfaHTfFJh4nJHo8Dd29qGEE0EACfYubQ
Egrj0otL38qswUHJriLOj4M=
=kfo5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-01-10 1:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 0:26 Simonovsky, Pavel
2002-01-06 3:48 ` Mo DeJong
2002-01-06 6:36 ` Ralf Corsepius
2002-01-07 12:04 ` Khamis Abuelkomboz
2002-01-07 13:11 ` Timothy M. Shead
2002-01-18 18:13 ` Mo DeJong
2002-01-07 13:22 ` Ian Roxborough
2002-01-07 13:34 ` Patches...[was: Re: SourceNav release ... ] Ian Roxborough
2002-01-10 4:34 ` Eray Ozkural (exa) [this message]
2002-01-11 14:34 ` SourceNav release Mo DeJong
2002-01-18 14:52 ` Eray Ozkural (exa)
2002-01-18 15:33 ` Mo DeJong
2002-01-18 15:58 ` Ian Roxborough
2002-01-24 10:14 ` Eray Ozkural (exa)
2002-01-19 9:03 ` Eray Ozkural (exa)
2002-01-19 8:59 ` Khamis Abuelkomboz
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 2:56 Roman Levenstein
2002-01-04 15:48 ` Khamis Abuelkomboz
2002-01-03 14:30 klmcw yahoo
2002-01-03 15:08 ` Khamis Abuelkomboz
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=E16OTwP-0000sV-00@orion.exa.homeip.net \
--to=erayo@cs.bilkent.edu.tr \
--cc=corsepiu@faw.uni-ulm.de \
--cc=irox@redhat.com \
--cc=kdevelop-devel@kdevelop.org \
--cc=snuffeler@gmx.net \
--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).