Re: [bug #16997] compiler warning for NSZone.m

[Peter Cooper]

On 2006-07-04 19:00:42 +0200 Richard Frith-Macdonald 
<richard@tiptree.demon.co.uk> 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

I think Patrick's bugs are real bugs - compiler warnings exist for a 
reason. Clean code bases lead to real risks being noticeable 
immediately, as opposed to skulking silently until causing weird 
errors or security problems.

Having these listed as bugs can also lead to people putting in bug 
fixes, getting them involved. I don't know the odds of that actually 
happening, but it's a good idea in principle(?) - the only risk is a 
small amount of code bloat where things like

  // avoid compiler warning for pre-allocating spare ivar
  i = 0;

would pop into quite a few classes. The more useful cases might 
include resolving the security warnings about dangerous tmpnames etc. 
I personally think that isn't a bad thing.

Peter