On Mon, 31 Mar 2003, Simon Wistow wrote: > It p*sses me off when I see C projects spewing out warnings during > compile. Why? Because they'll never get fixed. Not without some > gargantuan effort which could have been avoided by doing it before check > in.
The compile ones aren't so hard to fix. You know where they are. The tricky ones are the "glib: This pointer is NULL" ones, because you never know who should have set the pointer to something non-NULL. This is the issue referred to by me (earlier), Tim Sweetman (later) etc. It's also in my opinion the strongest argument for not disabling warnings at deployment. > And Fleeg dies. Poor Fleeg. Whoops. [weak anti-war joke snipped] S. -- Shevek http://www.anarres.org/ I am the Borg. http://design.anarres.org/
