On Tuesday 04 July 2006 13:00, Richard Frith-Macdonald wrote: > Hmm ... I started reclassifying these as category ';change request' > rather than 'bug' and severity 'wish' rather than 'normal' since > these are plainly not bugs, just (mostly) spurious compiler warnings. > However, I'm not sure that's the right thing to do ... > Should they be closed as 'invalid' instead? I'm inclined to think it > would be nice to change code to avoid spurious compiler warnings as a > very low priority issue, but perhaps others feel different?
Thats a bad idea because there very well could be an actual bug there. GCC just doesn't randomly warn you. Its better to actually fix these, then close them as invalid. Closing them as invalid, of course, would be marking them as not a bug, which as I just said, there may actually be buggy code there. Its better to actually fix the code that causes the warnings then close them thinking theres no bug. -- Patrick McFarland || www.AdTerrasPerAspera.com "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989 _______________________________________________ Bug-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnustep
