From: Eric Christopher <echristo@redhat.com>
To: berek@usa.net
Cc: sourcenav@sourceware.cygnus.com
Subject: RE: replace (plain text)
Date: Tue, 03 Jul 2001 22:54:00 -0000 [thread overview]
Message-ID: <994225972.6132.3.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <NFBBLPGOFICNAFDHEABHCEEKCDAA.berek@usa.net>
Berek,
I know that since I work at Red Hat my comments on this will be
quite suspect, however, I felt that since I've used SN on occasion
that I should at least comment here. SN has successfully parsed and
xref'd the code to gcc, libstdc++ and many of the other programs
that I work on here. To be honest, I haven't tried this out much
lately, but 3-6 mos ago when I last used the program it worked fine
as an analysis tool.
As a developer I'm sure that you only accept clear bug reports so
that you can fix the problems. The SN team I'm sure would
appreciate them as well. If you could provide code snippets that
won't xref then they could verify the bugs and make sure that they
work in the newer versions of the program.
Now, as far as bug reports against old versions of the software,
likely they'll be verified that they work in the new program and
that you'll be suggested to upgrade to the newest version available
from sources. Have you tried doing this and does it work for you?
-eric
On 03 Jul 2001 21:37:49 -0400, Berek Half-hand wrote:
> Mo, just started work at Unisphere Networks in Westford Mass. Code base at
> old place of work was all C++. Lots of parser and xref problems; you
> probably remember some of my email. New job all JAVA. Dbimp croaks, can't
> build xref, etc. My experience with SN is that it can't parse or build
> xref's for anything but the simplest of standard C code bases. It doesn't
> parse C++ or Java in any of the last three places I've worked at. And no, I
> can't let you have any of the code bases (they don't belong to me). No, I
> can't afford to pay Redstone to fix these problems (I paid $500 for SN 4.5.1
> one month before it went public domain, and I sort of figured bug fixing and
> maintenance were part of what I paid for). No, I can't fix these problems
> myself; I spend all of my time (50-60 hrs/week) bringing home a paycheck.
>
> 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?
>
--
I will not grease the monkey bars
next prev parent reply other threads:[~2001-07-03 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 7:02 replace Aurelian Melinte
2001-07-03 13:12 ` replace Mo DeJong
2001-07-03 13:54 ` replace Gacquer William
2001-07-03 14:45 ` replace Mo DeJong
2001-07-03 15:32 ` SN +gvim + ex-ctags == excellent free IDE Subrata Datta
2001-07-03 18:37 ` replace (plain text) Berek Half-hand
2001-07-03 22:54 ` Eric Christopher [this message]
2001-07-04 11:49 ` Mo DeJong
2001-07-04 12:09 ` Berek Half-hand
2001-07-04 15:11 ` Eric Christopher
2001-07-09 7:17 ` Aurelian Melinte
2001-07-04 13:52 ` Gacquer William
2001-07-04 14:38 ` Mo DeJong
2001-07-04 15:10 ` Gacquer William
2001-07-05 18:21 ` Mo DeJong
2001-07-06 13:41 ` Andrew Cagney
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=994225972.6132.3.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=berek@usa.net \
--cc=sourcenav@sourceware.cygnus.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).