This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: bugzilla clean ups
- From: Bud Davis <bdavis9659 at sbcglobal dot net>
- To: NightStrike <nightstrike at gmail dot com>
- Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
- Date: Sat, 15 Jun 2013 11:27:29 -0700 (PDT)
- Subject: Re: bugzilla clean ups
> Davis <bdavis9659@sbcglobal.net>
> wrote:
> > Hello All,
> >
> > There are some bug reports in bugzilla that are old and
> stale...what are the rules for closing them as "WONT FIX".
> >
> > The first example I ran across was
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22210
> >
> > Not too sure of the original problem, but it has been
> 6+ years.
> >
> > Can I terminate this one (and ones like it) ?
> >
> > Should some discussion hit the mailing list ?
>
> [Resending to list, caught in html mail trap]
>
> Just because a big hasn't been fixed in a while doesn't mean
> it should be
> closed. So no you should not just close old bugs as won't
> fix for the sole
> reason that they are old.
>
Sure, I agree with that, and I agree with Steve's comment.
In this example, the title is:
"gfc_conv_array_initializer weirdness"
which initially is something in the source code that seems incorrect. This gets tossed around for a couple of years, then there is a snippet of code that is not compilable that may or may not demonstrate there is a problem.
What is there to work on ? I really cannot discern from the initial bug report or the trail of comments.
Guess I kind of answered my own question. If the 'problem' is not well defined enough to know what is wrong, then no one should object to closing it. Not like it cannot be re-opened.
--bud