From: Ben Elliston <bje@redhat.com>
To: Berek <berek@usa.net>
Cc: sourcenav@sources.redhat.com
Subject: Re: SN Enterprise 4.5 (99 R1)
Date: Sun, 03 Sep 2000 15:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0009040938540.31493-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <NDBBJEBJPMNFKBGLKCNFGEFHEJAA.berek@usa.net>
I've found lots of bugs using SN Ent 4.5 (99 R1). Most important are
those that occur when parsing a large C++ code base (see attached MS
Word doc). Seems to be a problem with TCL Notifier, but I have no TCL
files. This is a very serious problem for my company. Bottom line is
that we can't use SN with our code base. Is this a known problem? Can
you tell me when the next/latest bug fix version will be available?
S-N has parsed *very large* C++ projects in the past. I suspect a small
number of C++ constructs in your project are causing the problem with the
C++ parser. Can you determine where the problem lies by parsing fewer and
fewer files in S-N? Then you should be able to post a small test case.
And please don't post binary attachments to the mailing list.
Cheers, Ben
prev parent reply other threads:[~2000-09-03 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-03 14:13 Berek
2000-09-03 15:41 ` Ben Elliston [this message]
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=Pine.LNX.4.21.0009040938540.31493-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=berek@usa.net \
--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).