From: "Richard F Weber" <rfweber@link.com>
To: David Capel <capes@robots.ox.ac.uk>
Cc: sourcenav@sources.redhat.com
Subject: Re: auto completion
Date: Mon, 16 Apr 2001 12:52:00 -0000 [thread overview]
Message-ID: <3ADB4D6B.5040106@link.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010413120619.6326B-100000@kate>
Speaking of which, this brings up a small problem I conveniently ignored
when working on my parser. Is there a way to search for symbols in a
given set of files?
For example, in Ada, you can "Use" a file (basically include it), and
then do a "with" to reduce the namespace. This tends to make it tough
if you do a "Use pkg_a; with pkg_a" & "Use pkg_b; with pkg_b", and a
call is made to a function called "func1". Which package do you
reference to? How do you know if "func1" belongs to pkg_a or pkg_b?
I did find a routine called get_symbol, but I'm having a heck of a time
trying to figure out how to call it right, and what is necessary. Is
there any other routine I can use to do quick queries like that against
the database, or will I have to dig into the DB_API to write my own?
This seems to tie right in because the editor could be set-up to analyze
on the fly which files are included in, and offer those symbols as
automatic completion for the end-user to use.
Thanks.
--Rich
David Capel wrote:
>Are there any plans to add tab-completion on symbol names in the editor,
>along the lines of the Emacs "hippie-expand" packages? ( Or does this
>feature already exist and I've missed it? ) I work with a set of C++
>libraries which have some very long class/member/function names, and
>this feature is indispensible.
>
>Source Navigator is a great project. Keep up the good work!
>
>David
>
>
>
next prev parent reply other threads:[~2001-04-16 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <987159756.5333.ezmlm@sources.redhat.com>
2001-04-13 4:13 ` David Capel
2001-04-16 12:52 ` Richard F Weber [this message]
2001-04-17 9:53 ` Ian Roxborough
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=3ADB4D6B.5040106@link.com \
--to=rfweber@link.com \
--cc=capes@robots.ox.ac.uk \
--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).