Re: Power of the G++ test suite

[Mark Mitchell <mark at markmitchell dot com>]

>>>>> "Carlo" == Carlo Wood <carlo@runaway.xs4all.nl> writes:

    Carlo> I am sorry to bring this up again, but what is wrong with
    Carlo> the test I contributed for the g++ test suite?  After the

Probably nothing.

    Carlo> what is already there".  All I ask for is an official
    Carlo> comment on this test case and the reason why it is ignored.
    Carlo> If the reason is that the "official guys", which should
    Carlo> make the decision and/or comment, want me to leave this
    Carlo> project then please just say so - preferably in public with
    Carlo> the reason for it - and I will do so.

I am not an "official guy", but I am a frequent contributor to the GCC
project.  Of course, we don't want you to "leave this project".
Speaking only for myself, I recommend that you develop a bit more
patience.  Personally, I almost always add test-cases when I *fix*
bugs, not when I *find* them; that way, I know that the work I've done
to fix the bug won't be undone by myself, or someone else, at a later
date.  That's not to say that no-one will add the test case until they
fix the bug; it's just a comment on my own behavior.  I save every bug
report, so, at some point, I'll probably get around to fixing the bug,
if someone else doesn't.

It takes time for us to fix bugs, incoporate test cases, and so forth.
At present much of the team is working on getting the 1.1 release
together.  Many of us, in one way or another, make at least part of
our living working on GCC.  That means that we must do what our
customers would like, rather than what you would like, at any given
moment.  You can of course avoid this situation by hiring someone to
do the things that you would like. :-) Even those generous enough to
volunteer their time must prioritize what to do at any given point.

In summary, I suspect that if you calm down and wait patiently, your
test case will indeed be added to the test suite.

-- 
Mark Mitchell 			mark@markmitchell.com
Mark Mitchell Consulting	http://www.markmitchell.com