RE: [TCLCORE] warnings as errors for debug builds - good reason?

[John O. <ou...@el...>]

Sorry for entering this discussion so belatedly, but it seems to me
that there are two approaches that make sense:

1. We care about having warning-free compiles.  In this case, turning
warnings into errors is helpful, since it ensures that they get fixed
immediately.

2. We don't care about having warning-free compiles.  In this case,
there's no need to turn them into errors.

I'm having trouble coming up with a scenario where you'd want approach
#1 but wouldn't want warnings turned into errors.  This feels like a
slippery slope where you'll end up with zillions of warnings.
Personally,
I think it's better to retain the flags that turn warnings into errors.

-John-

> -----Original Message-----
> From: tcl...@li... 
> [mailto:tcl...@li...] On Behalf Of Jeff Hobbs
> Sent: Thursday, August 07, 2003 2:55 PM
> To: tcl...@li...
> Subject: [TCLCORE] warnings as errors for debug builds - good reason?
> 
> 
> The default flags for Tcl and TEA have warnings act as errors on
> Windows builds (not unix ones).  This may have been important once
> upon a time ... but do we really need it anymore?  While we do
> strive to not have any warnings in core builds anyway, I don't see
> the value in forcing these as errors.
> 
> Jeff