Re: How to get ORCA/C bugs fixed.

[bird@nwsrs.nw.att.com (J. L. Walters)]

In article <1994Oct22.050412.6271@chemabs.uucp>,  <lvirden@cas.org> wrote:
>
>So bugs which can not be narrowed down to simple test cases should just
>be bore silently.  Grit your teeth and say "There's no place like source;
>there's no place like source...".

Larry,

Love the Wizard of Oz reference, however, I do think that the sense of
the previous post was that Mike receives TONS of complaints/reports
that he cannot reproduce from the description so he has fallen back to
using only those reports that give a bug in a fashion he can reproduce.

The good news is, he spends his time fixing real problems.

The bad news is, he doesn't look at those problems that are random in
nature and are really nasty because of this. I don't have any direct
input except my experience in supporting a very large software project
that was used by non-computer geeks. I tended to do exactly as reported
for Mike, however, I did make a mental note of the nature of the "I
don't have a clue what caused the problem, but here are its
attributes." When a pattern emerged I did start looking into the
problem with more intensity.
-- 

		Joe Walters att!nwsrs!bird NW 31K14 (708) 224-7189
		To know, and not to do, is not yet to know.