Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!usc!cs.utexas.edu!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: Compiler bug reporing (was: Re: Zortech bug #24)
Message-ID: <1520@lupine.NCD.COM>
Date: 11 Sep 90 06:10:45 GMT
References: <17.26EA603B@ananke.stgt.sub.org> <1430@proto.COM>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 36

In article <1430@proto.COM> joe@proto.COM (Joe Huffman) writes:
>In article <17.26EA603B@ananke.stgt.sub.org>, kaiser@ananke.stgt.sub.org 
>(Andreas Kaiser) writes:
>
>[...Bug report for Zortech C++ compiler...]
>
>You may mail your bug reports to the engineers, tech support, and tech
>writers by sending them to 'zortech-bugs@proto.com' or 
>'uunet!proto!zortech-bugs'.  Posting them on the net is probably 
>inappropriate most of the time.

I could not disagree more.  I have in the past posted innumerable bug
reports on various C++ language processors here (mostly for cfront and
for g++).  Many readers of this newsgroup have thanked me for this effort
to make both users and vendors aware of the current shortcommings of
these C++ language processor products.  I hope to find time to do more of
this in the future.

One thing is certain.  Expecting C++ vendors to come clean and publically
admit the true number and severity of bugs in their own products is kinda
like expecting the fox to guard the chicken coop.

If seeing bug reports for your products posted to the net bothers you, I
believe that there is a simple solution.  It's called testing.

In the meantime, I personally would like to encourage everyone to post
(carfully considered) bug reports to this newsgroup.  I (for one) have
been saving each and every one of these for quite some time.  I hope
to have the time (one of these days) to go back over the year + worth
of reports that I have saved and add them all to my own set of compiler
test cases.
-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.