Re: xref and referred by?

["Berek" <berek@usa.net>]

I've experienced the same problem frequently (declaration vs
implementation).

----- Original Message -----
From: <dave.banham@tde.alstom.com>
To: <sourcenav@sources.redhat.com>
Sent: Thursday, October 19, 2000 04:19
Subject: Re: xref and referred by?


>
>
> My project is 100% (embedded) C code and I still have problems with xref.
I hope
> that when the C++ parser is fixed that the C parsing capabilities will be
> improved too.
>
> BTW, I notice that sometimes when I right click on a variable in the
editor
> window and select Find Implementation of 'xyz' that nothing happens, but
when I
> select Find Declaration of 'xyz' SN puts up a window asking me choose one
of two
> files to view. The first file is always a .h file and when selected it
shows a
> line with the variable declared extern. Whilst the second file is the .c
and
> shows the line where the variable is implemented (or is that declared?) If
I
> then click on the variable's declared type (which is a typedef'd type),
Find
> Implementation does nothing and Find Declaration switches (correctly) to
the
> file containing the typedef statement for the type. If I now repeat this
for the
> type name (in the typedef statement), Find Implementation does nothing and
Find
> Declaration highlights the type name. Using Xref on the type name, shows
that
> xref doesn't know where the type is used either.
>
> Oddly enough, Find Implementation and Find Declaration work fine for
function
> names, as does Xref. Is the cross-reference information broken for
variables and
> types or was it never intended to cover variables and types? (If so why
not?)
>
> Regards
> Dave Banham
>
>
>
>
>
> "Berek" <berek@usa.net> on 18/10/2000 16:00:37
>
> Please respond to "Berek" <berek@usa.net>
>
> To:   Dave BANHAM/PCS/PCG/TDE/GECALSTHOM@GA
> cc:
> Subject:  Re: xref and referred by?
>
>
>
> The xref seems to be pretty good with std C; however, it's not reliable
with
> C++, and no, you can't rely on it even if it's reporting some references.
> Until they eliminate the C++ parsing problems, you'll have to keep
verifying
> xrefs with grep.
>
> ----- Original Message -----
> From: <dave.banham@tde.alstom.com>
> To: "sourcenav" <sourcenav@sources.redhat.com>
> Sent: Wednesday, October 18, 2000 04:02
> Subject: Re: xref and referred by?
>
>
> >
> >
> > I too have also experienced this frustrating problem and I don't believe
> it is
> > anything to do with the fact that the xref database is still being
> > (re-)constructed - at least there is no progress bar indication.
> >
> > I quite often end up using the grep tool to find the references - which
it
> does
> > - but in doing so I am left questioning the accuracy of the xref tool.
If
> xref
> > reports no referenced by information then I will try grep, but if it
> reports
> > some referenced by information am I seeing the complete picture or just
> part of
> > it?
> >
> > Regards
> > Dave Banham
> >
> >
> >
> >
> >
> > Bruce Stephens <bruce.stephens@messagingdirect.com> on 17/10/2000
16:45:41
> >
> > To:   sourcenav <sourcenav@sources.redhat.com>
> > cc:    (bcc: Dave BANHAM/PCS/PCG/TDE/GECALSTHOM)
> > Subject:  Re: xref and referred by?
> >
> >
> >
> > Lonnie L VanZandt <tsys@uswest.net> writes:
> >
> > > Why is it that many times the Referenced By information is
> > > unavailable? More often than not, I want to see who calls a function
> > > and not what that function calls. However, I can't seem to get SN to
> > > display the Referenced By information.
> >
> > xref requires that certain databases be completely constructed.  The
> > first time you run source navigator on a project, these can take some
> > time to construct (potentially hours, for large projects and/or slow
> > machines).  There's a progress bar in the bottom right corner of any
> > SN windows while this is going on.
> >
> > After the first time, SN should be faster to start up.
> >
> > --
> > Bruce Stephens           Bruce.Stephens@MessagingDirect.com
> > MessagingDirect(UK) Ltd       <URL: http://www.MessagingDirect.com/ >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>