RE: replace (plain text)

["Berek Half-hand" <berek@usa.net>]

You refer to the fact that SN is incapable of producing a xref for any of
the C++ and Java code bases I've worked on for the past 3 1/2 years as "a
bug"? That it's not as important as upgrading to TCL/TK 8.3? Frankly, IMHO,
the xref capability of SN is by far the most important feature of the
product. Of all the tools that allow people to come up to speed on a new
code base and for understanding new and existing functionality, the xref is
by far the most useful and important. I've only seen SN xref work on the
most trivial of code bases. You call this "whining" [smile]? And, BTW, it's
not one bug. it's many.

I just sent a small part of my latest code base to a cohort of yours in the
UK. I included screen captures of a couple of bugs, including (MS Visual
Studio) memory, registers, error messages, disassembly at the location of
the error (access violation in dbimp) and all of the source code he needed
to reproduce and solve the problem. His response was that it was too much
info for him to download and that he was reluctant to receive source code
that didn't belong to me (it belongs to my employers). He then asked me if I
could provide him with an "example" of the source code that caused the
problem [AAAAARRRRRGGGGGHHHHH!!!!!]. Is there something wrong with this or
is it me?

-----Original Message-----
From: sourcenav-owner@sources.redhat.com
[ mailto:sourcenav-owner@sources.redhat.com]On Behalf Of Mo DeJong
Sent: Wednesday, July 04, 2001 2:49 PM
To: sourcenav@sourceware.cygnus.com
Subject: RE: replace (plain text)


On Tue, 3 Jul 2001, Berek Half-hand wrote:

....

> So...instead of talking about code base search and replace, why doesn't
> someone at RedHat fix some of these serious problems? I haven't been able
to
> get an xref of any code base in any language (except a simple std C grep I
> wrote years ago) for over three years. Pardon my frustration, but I really
> wish I had my money back. Any chance of that?

Frankly, I am not sure how to respond to your email. I seem to remember
explaining options that folks had when faced with a bug on this list
a number of times. Whining about a bug is not really the most effective
course of action.

Just because you don't see any improvement in a specific set of bugs
does not mean that we are not fixing things. Currently, we are working
on the Tcl/Tk 8.3 upgrade and getting CVS access setup. This work
is much more important then the parsers. The parsers need work, it
is a know issue and it is likely one that will never be solved to
everyone's satisfaction (since everyone wants something different).

Mo DeJong
Red Hat Inc