From: Syd Polk <spolk@redhat.com>
To: <sourcenav@sources.redhat.com>
Subject: Re: Source navigator roadmap, features list, etc.?
Date: Thu, 28 Sep 2000 13:26:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20000928132656.00bbce50@pop.cygnus.com> (raw)
In-Reply-To: <002a01c02967$3c4e7940$7113a8c0@concord.com>
At 12:14 PM 9/28/00 -0400, Berek wrote:
>I've experienced the same problem with SN (4.5.1 and 4.5.2). C++ Xref is not
>reliable. Often have to fall back on GREP. For me, this is probably the most
>serious problem I have with SN.
>
>Also, xref for local variables doesn't seem to work at all. Nor does
>locating the declaration of local variables. Yes, I do have "generate
>references to local variables" checked in XRef preferences.
These are known problems. Hopefully, we can address them soon, or somebody
in the community can dig into it.
>----- Original Message -----
>From: "Bruce Stephens" <bruce@cenderis.demon.co.uk>
>To: <sourcenav@sources.redhat.com>
>Sent: Wednesday, September 27, 2000 16:44
>Subject: Re: Source navigator roadmap, features list, etc.?
>
>
> > William Gacquer <wgacquer@ubisoft.fr> writes:
> >
> > [...]
> >
> > > 16/ what else?.... uhhh, I am sure I have missed something....
> >
> > More/better parsers. Emacs lisp is an obvious one, but more
> > immediately PHP would be *really* handy.
> >
> > Possibly there are significant limitations of many of the existing
> > parsers, but the one that's really annoying us at the moment is C++:
> > it seems that often, trying to xref methods gives nothing at all
> > useful (indeed, often nothing at all). Presumably this is because the
> > C++ parser isn't up to the job.
> >
Syd Polk spolk@redhat.com
Engineering Manager +1 415 777 9810 x 241
Red Hat, Inc.
next prev parent reply other threads:[~2000-09-28 13:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Thomas>
[not found] ` <Heller's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Tue,>
[not found] ` <"Wed,>
[not found] ` <"Fri,>
[not found] ` <15>
[not found] ` <"Mon,>
[not found] ` <20>
[not found] ` <"Thu,>
[not found] ` <3>
[not found] ` <Aug>
[not found] ` <2000>
[not found] ` <15:23:58>
[not found] ` <-0800>
[not found] ` <Mo>
[not found] ` <05:03:28>
[not found] ` <-0700>
2000-09-15 5:06 ` SN452 Installation Rouviere, Stephane
2000-09-15 5:24 ` Bruce Stephens
2000-09-15 11:20 ` Syd Polk
[not found] ` <18:21:47>
[not found] ` <+0200>
2000-08-03 9:22 ` Getting started with tcl Thomas Heller
2000-08-03 9:40 ` Bruce Stephens
2000-08-03 10:19 ` Syd Polk
2000-09-27 1:12 ` Source navigator roadmap, features list, etc.? William Gacquer
2000-09-27 22:16 ` Bruce Stephens
2000-09-28 9:15 ` Berek
2000-09-28 13:26 ` Syd Polk [this message]
2000-09-28 13:22 ` Syd Polk
2000-10-03 16:02 ` Mo DeJong
2000-10-04 10:25 ` Syd Polk
2000-10-04 13:27 ` SN Printing Under WIN/NT Berek
2000-10-04 15:27 ` Mo DeJong
2000-10-04 16:50 ` Paul Selormey
2000-10-04 17:04 ` Mo DeJong
2000-10-05 12:06 ` Syd Polk
2000-10-05 13:13 ` Berek
2000-11-20 4:47 future plans Simone Contini
2000-11-20 12:02 ` Syd Polk
2000-11-20 15:24 ` Mo DeJong
2000-11-20 15:37 ` Timothee Besset
2000-11-21 11:02 ` Mo DeJong
2000-11-20 16:13 ` Tom Tromey
2000-11-21 12:22 ` Syd Polk
2000-11-21 12:31 ` Mo DeJong
2000-11-21 12:32 ` Tom Tromey
2000-11-21 15:18 ` Bruce Stephens
2000-11-21 15:47 ` Tom Tromey
2000-11-21 15:41 ` Syd Polk
-- strict thread matches above, loose matches on Subject: below --
2000-10-05 1:16 Source navigator roadmap, features list, etc.? William Gacquer
2000-10-05 0:52 dave.banham
2000-10-04 0:53 leonp
2000-10-04 2:42 ` Timothy M. Shead
2000-09-29 0:26 dave.banham
2000-09-29 11:32 ` Syd Polk
2000-09-28 0:23 dave.banham
2000-09-28 13:25 ` Syd Polk
2000-09-28 17:28 ` Ben Elliston
2000-09-29 6:06 ` Bruce Stephens
2000-09-25 22:04 Timothee Besset
2000-09-26 9:23 ` Syd Polk
2000-09-26 10:30 ` Berek
2000-09-26 10:37 ` Syd Polk
2000-09-27 21:41 ` Ben Elliston
2000-10-03 9:44 ` Mo DeJong
[not found] <Syd>
[not found] <Rouviere,>
[not found] <William>
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=4.2.0.58.20000928132656.00bbce50@pop.cygnus.com \
--to=spolk@redhat.com \
--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).